-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AWS Lambda Integration: async handler #677
Comments
By itself, hopefully not. But if we go ahead to replace all the callback code in the package with promises, then perhaps. |
We are not replacing all code with promises in this PR but we are going to be returning a promise-based lambda handler instead of callback-based. |
* change lambdaHandler wrapper to return async handler #677 * aws lambda example project * README in example project and CHANGELOG * add temp logs * fix README * throw err in afterNotify * debugging new aws lambda handler impl * debugging new aws lambda handler impl * adding logs * wip * wip * remove aws default listener * remove aws default listener * remove logs * remove logs * #327 notifyAsync (#684) * notifyAsync + tests * simplify implementation * changelog * add test * revert to original implementation + test * update tests * return isomorphic handler + tests * make input and output generic in handler * use any so users will not be forced to specify type * CHANGELOG.md * aws lambda example project, point to future version
This has been released with v4 (currently in beta). |
Discussed in #674
Improve implementation of callback based and async (promise based) lambda handlers.
Question: Should this be a major release?
The text was updated successfully, but these errors were encountered: