-
Notifications
You must be signed in to change notification settings - Fork 146
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
Feature request: Export APIGatewayV2RequestAuthorizer & APIGatewayV2RequestContext schemas #3182
Comments
Hi @codyfrisch, thanks for opening this issue. I think it makes sense to export them, I'm adding this to the backlog. If you'd like to open a PR to get it done, I'd be happy to help you merge it. Otherwise we'll get to it before next release in ~2 weeks. |
I'll let you do it. (I'll start contributing eventually). In the meantime, I created duplicates to keep me going until this is released. |
This issue is now closed. Please be mindful that future comments are hard for our team to see. If you need more assistance, please either tag a team member or open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so. |
This is now released under v2.11.0 version! |
Use case
I need to parse the actual structure of an APIGatewayProxyEventV2Schema's requestContext.authorizer.lambda key (for both typing and validation reasons)
Solution/User Experience
Export the APIGatewayV2RequestAuthorizer & APIGatewayV2RequestContext schemas so that APIGatewayV2RequestAuthorizer can be extended with a custom schema for the lambda authorizer, and in turn extend APIGatewayV2RequestContext with that schema (and in turn extend APIGatewayProxyEventV2Schema).
Alternative solutions
No response
Acknowledgment
Future readers
Please react with 👍 and your use case to help us understand customer demand.
The text was updated successfully, but these errors were encountered: