You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since version 0.3.0 we have support for async/await in middlewares.
We could potentially apply the same approach to the handler. Since the handler is invoked and managed by the middy wrapper, we could support different syntaxes including handlers returning promises and consequently async/await handlers.
These are the two syntaxes I envision might be cool to support:
Since version
0.3.0
we have support forasync/await
in middlewares.We could potentially apply the same approach to the handler. Since the handler is invoked and managed by the middy wrapper, we could support different syntaxes including handlers returning promises and consequently
async/await
handlers.These are the two syntaxes I envision might be cool to support:
and, with
async/await
:Any thoughts?
I think this is feasible by addressing the handler runtime logic here.
The text was updated successfully, but these errors were encountered: