-
Notifications
You must be signed in to change notification settings - Fork 402
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(event-handler): multi-value query string and validation of scalar parameters #3795
Conversation
aws_lambda_powertools/utilities/data_classes/api_gateway_proxy_event.py
Outdated
Show resolved
Hide resolved
tests/functional/event_handler/test_openapi_validation_middleware.py
Outdated
Show resolved
Hide resolved
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.
tiny changes
9762c66
to
fe32522
Compare
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.
pre-approving, lemme know if more changes and I can approve again (I think only testing globals are left)
Quality Gate passedIssues Measures |
@heitorlessa reasking for a review since I did a lot of changes |
Issue number: #3732
Summary
Changes
This PR fixes a bug when validating scalar parameters. After the code we've introduced to handle multiple parameters, the code become inconsistent (notice the
Any
type) in that some resolvers return scalar parameters and some others returned a list of parameters.This caused problems when handling validation of scalar parameters. This code fixes that by ensuring the same behaviour in all event handlers, and updating the types accordingly.
User experience
This PR will fix the issue on #3732
Checklist
If your change doesn't seem to apply, please leave them unchecked.
Is this a breaking change?
RFC issue number:
Checklist:
Acknowledgment
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.