Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Obtaining the return type of a function

I have the following function:

function test(): number {
    return 42;
}

I can obtain the type of the function by using typeof:

type t = typeof test;

Here, t will be () => number.

Is there a way to obtain the return type of the function? I would like t to be number instead of () => number.

like image 508
rid Avatar asked Mar 15 '16 15:03

rid


People also ask

How do you find the return type of a function?

We can return any value from the function like string, number, any, character, etc. To define the return type for the function, we have to use the ':' symbol just after the parameter of the function and before the body of the function in TypeScript.

What is return type of a function call?

A return statement ends the execution of a function, and returns control to the calling function. Execution resumes in the calling function at the point immediately following the call. A return statement can return a value to the calling function.

What is return type in JavaScript?

Definition and Usage. The return statement stops the execution of a function and returns a value. Read our JavaScript Tutorial to learn all you need to know about functions.

Can functions return any type?

A function may be defined to return any type of value, except an array type or a function type; these exclusions must be handled by returning a pointer to the array or function. When a function does not return a value, void is the type specifier in the function declaration and definition.


7 Answers

EDIT

As of TypeScript 2.8 this is officially possible with ReturnType<T>.

type T10 = ReturnType<() => string>;  // string
type T11 = ReturnType<(s: string) => void>;  // void
type T12 = ReturnType<(<T>() => T)>;  // {}
type T13 = ReturnType<(<T extends U, U extends number[]>() => T)>;  // number[]

See this pull request to Microsoft/TypeScript for details.

TypeScript is awesome!


Old-school hack

Ryan's answer doesn't work anymore, unfortunately. But I have modified it with a hack which I am unreasonably happy about. Behold:

const fnReturnType = (false as true) && fn();

It works by casting false to the literal value of true, so that the type system thinks the return value is the type of the function, but when you actually run the code, it short circuits on false.

like image 70
thedayturns Avatar answered Oct 04 '22 06:10

thedayturns


The easiest way in the TypeScript 2.8:

const foo = (): FooReturnType => {
}

type returnType = ReturnType<typeof foo>;
// returnType = FooReturnType
like image 43
Jaroslav Avatar answered Oct 04 '22 04:10

Jaroslav


The code below works without executing the function. It's from the react-redux-typescript library (https://github.com/alexzywiak/react-redux-typescript/blob/master/utils/redux/typeUtils.ts)

interface Func<T> {
    ([...args]: any, args2?: any): T;
}
export function returnType<T>(func: Func<T>) {
    return {} as T;
}


function mapDispatchToProps(dispatch: RootDispatch, props:OwnProps) {
  return {
    onFinished() {
      dispatch(action(props.id));
    }
  }
}

const dispatchGeneric = returnType(mapDispatchToProps);
type DispatchProps = typeof dispatchGeneric;
like image 28
eug Avatar answered Oct 04 '22 06:10

eug


There isn't a way to do this (see https://github.com/Microsoft/TypeScript/issues/6606 for the work item tracking adding this).

A common workaround is write something like:

var dummy = false && test();
type t2 = typeof dummy;
like image 38
Ryan Cavanaugh Avatar answered Oct 04 '22 06:10

Ryan Cavanaugh


Edit: This is not needed with TS 2.8 any more! ReturnType<F> gives the return type. See accepted answer.


A variant on some of the previous answers that I'm using, which works in strictNullChecks and hides the inference gymnastics a bit:

function getReturnType<R>(fn: (...args: any[]) => R): R {
  return {} as R;
}

Usage:

function foo() {
  return {
    name: "",
    bar(s: string) { // doesn't have to be shorthand, could be `bar: barFn` 
      return 123;
    }
  }
}

const _fooReturnType = getReturnType(foo);
export type Foo = typeof _fooReturnType; // type Foo = { name: string; bar(s: string): number; }

It does call the getReturnType function, but it does not call the original function. You could prevent the getReturnType call using (false as true) && getReturnType(foo) but IMO this just makes it more confusing.

I just used this method with some regexp find/replace to migrate an old Angular 1.x project that had ~1500 factory functions written like this, originally in JS, and added the Foo etc types to all uses... amazing the broken code one will find. :)

like image 30
Aaron Beall Avatar answered Oct 04 '22 04:10

Aaron Beall


Use built-in ReturnType:

type SomeType = ReturnType<typeof SomeFunc>

ReturnType expands to:

type ReturnType<T extends (...args: any) => any> = T extends (...args: any) => infer R ? R : any;
like image 25
z0gSh1u Avatar answered Oct 04 '22 04:10

z0gSh1u


If the function in question is a method of a user defined class, you can use method decorators in conjuction with Reflect Metadata to determine the return type (constructor function) at runtime (and with it, do as you see fit).

For example, you could log it to the console:

function logReturnType(
    target: Object | Function,
    key: string,
    descriptor: PropertyDescriptor
): PropertyDescriptor | void {
    var returnType = Reflect.getMetadata("design:returntype", target, key);

    console.log(returnType);
}

Just snap this method decorator on a method of your choice and you have the exact reference to the constructor function of the object that is supposedly returned from the method call.

class TestClass {
    @logReturnType // logs Number (a string representation)
    public test(): number {
        return 42;
    }
}

There are a few notable limitations to this approach, however:

  • you need to explicitly define the return type on a method decorated as such, otherwise you'll get undefined from Reflect.getMetadata,
  • you can only reference actual types which also exist after compilation; that is, no interfaces or generics

Also, you'll need to specify the following command line arguments for the typescript compiler, because both decorators and reflect metadata are experimental features as of writing this post:

--emitDecoratorMetadata --experimentalDecorators
like image 20
John Weisz Avatar answered Oct 04 '22 06:10

John Weisz