Merge pull request #47 from onicagroup/issue40

Issue #40 - Type error in LambdaUtils and in example

Author: kernwig

docs/source/lambda_utils.rst

@@ -72,7 +72,7 @@ General use
     export const hello = LambdaUtils.wrapApiHandler(async (event: LambdaUtils.APIGatewayProxyEvent) => {
         // These event objects are now always defined, so don't need to check for undefined. 🙂
         const who = event.pathParameters.who;
-        const points = parseInt(event.queryStringParameters.points || 0);
+        let points = Number(event.queryStringParameters.points || '0');
 
         if (points > 0) {
             let message = 'Hello ' + who;

lambda-utils/lib/lambda-utils.ts

@@ -10,9 +10,6 @@ import {Logger} from "@sailplane/logger";
 
 const logger = new Logger('lambda-utils');
 
-/** Define the async version of ProxyHandler */
-export type AsyncProxyHandler = (event: APIGatewayEvent, context: Context) => Promise<any>;
-
 /**
  * Casted interface for APIGatewayProxyEvents as converted through the middleware
  */
@@ -33,6 +30,9 @@ export interface APIGatewayProxyEvent extends AWS_APIGatewayProxyEvent {
     queryStringParameters: { [name: string]: string };
 }
 
+/** Define the async version of ProxyHandler */
+export type AsyncProxyHandler = (event: APIGatewayProxyEvent, context: Context) => Promise<any>;
+
 /**
  * Middleware to handle any otherwise unhandled exception by logging it and generating
  * an HTTP 500 response.