-
Notifications
You must be signed in to change notification settings - Fork 148
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
fix(parser): LambdaFunctionUrl envelope assumes JSON string in body #3514
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work on the envelope, left a few minor comments on the tests & test events.
One is a redundant test case (I think), and all the others are consistency/style.
Quality Gate passedIssues Measures |
Thank for the review, I have addressed the test names and comments. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Amazing, thanks for the PR - onto the next one!
Summary
Changes
This PR fixes the issues of
LambdaFunctionUrlEnvelope
assumedbody
field was always a JSON string. I have changed the Envelope similar to ApiGatewayV2 impementation and moved the example events according to the new convention.Issue number: closes #3199
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.