Feature Request: Export Mux when generating typescript server
#1342
Comments
fangyi-zhou
added a commit
to fangyi-zhou/smithy-typescript
that referenced
this issue
Jul 18, 2024
Closes smithy-lang#1342 It's useful to export the multiplexer that is automatically generated for a service, e.g. for use in anauthorizor lambda. This commit exports the generated multiplexer that is generated inside the service handler so that the multiplexer can be used in other packages.
fangyi-zhou
added a commit
to fangyi-zhou/smithy-typescript
that referenced
this issue
Jul 18, 2024
Closes smithy-lang#1342 It's useful to export the multiplexer that is automatically generated for a service, e.g. for use in anauthorizor lambda. This commit exports the generated multiplexer that is generated inside the service handler so that the multiplexer can be used in other packages.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello team,
We're using Smithy TypeScript server code generator for an AWS lambda function, and it's been working greatly. We've recently encountered a use case where we're trying to write an authorizer lambda for the lambda function that is dependent on the HTTP path. We've noticed that the default code generation provides a
Muxinsideget$OPERATIONHandlerandget$SERVICEHandler, and it looks like we can reuse theMuxfor implementing our authorizer lambda. Is it possible to export theMuxin a separate function?Thanks!
The text was updated successfully, but these errors were encountered: