Use Context rather than APIGatewayEventRequestContext (#13)

* Use Context rather than APIGatewayEventRequestContext Note: APIGatewayEvent is deprecated and APIGatewayProxyEvent should be preferred. I also added the APIGatewayProxyResult type to the handler as I think this is useful to have in the example - it will fail to compile if the returned value is missing attributes. APIGatewayEventRequestContext is available on event.requestContext, it's not the second argument for the handler. * Trigger CI * Also trigger CI on PR * Revert last commit Co-authored-by: Luca Casonato <[email protected]>
lucacasonato · Feb 8, 2020 · c407cc2 · c407cc2
1 parent 255f461
commit c407cc2
Show file tree

Hide file tree

Showing 2 changed files with 11 additions and 7 deletions.
diff --git a/README.md b/README.md
@@ -21,9 +21,12 @@ If you're unfamiliar with now runtimes, please read the [runtime docs](https://z
 
 ```ts
 // api/hello.ts
-import { APIGatewayEventRequestContext, APIGatewayEvent } from 'https://deno.land/x/lambda/mod.ts';
+import { APIGatewayProxyEvent, APIGatewayProxyResult, Context } from 'https://deno.land/x/lambda/mod.ts';
 
-export async function handler(event: APIGatewayEvent, context: APIGatewayEventRequestContext) {
+export async function handler(
+  event: APIGatewayProxyEvent,
+  context: Context
+): Promise<APIGatewayProxyResult> {
   return {
     statusCode: 200,
     body: `Welcome to deno ${Deno.version.deno} 🦕`,

diff --git a/example/api/version.ts b/example/api/version.ts
@@ -1,12 +1,13 @@
 import {
-  APIGatewayEventRequestContext,
-  APIGatewayEvent,
+  APIGatewayProxyEvent,
+  APIGatewayProxyResult,
+  Context,
 } from 'https://deno.land/x/lambda/mod.ts';
 
 export async function handler(
-  event: APIGatewayEvent,
-  context: APIGatewayEventRequestContext
-) {
+  event: APIGatewayProxyEvent,
+  context: Context
+): Promise<APIGatewayProxyResult> {
   return {
     statusCode: 200,
     body: `Welcome to deno ${Deno.version.deno} 🦕`,