Improve the parsing of values coming from headers #1483
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Unfortunately, the Route53 implementation in localstack is broken: localstack/localstack#5639 (comment) |
stof
force-pushed
the
better_value_parsing
branch
from
0db3b2b to
d6203c1
Compare
|
OK, I removed the commit fixing the handling of required parameters coming from headers for now. I will re-submit it separately to be able to handle the case of the route53 integration tests separately. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
FILTER_VALIDATE_INT, as done when reading from JSON or XML bodiesnullas fallback in the Result object (consistent with the behavior in JSON or XML bodies)Relates to #1481