TypeScript definition inconsistent with Lambda funcionality and lambda-api implementation

[geovanisouza92]

At this line the definition doesn't accept the callback param, and returns an anemic type, instead of a promise, breaking general TS type checking, forcing the consumers to cast the return or force the callback param.

Beyond that, the typing is not aligned with the examples in README.

[harshit-yadav]

Any update on this ?

[jeremydaly]

Hi @geovanisouza92, Typescript support was generously added by members of the community.

I can see the issue with the callback, but can you provide more detail regarding the other examples?

[geovanisouza92]

The run method should have the signature:

export default class API {
  // ...

  run(event: APIGatewayEvent, context: Context, cb: (err: Error, result: any) => void): void;
  run(event: APIGatewayEvent, context: Context): Promise<any>;

}

This way it would be aligned with lambda's handler signature and run method functionality.

---

Porting to TS would be awesome, but there's a mode where TS can automatically emit the signature, while reading from pure JS.