fix: parse patternproperties correctly when handling query parameters #1502
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
paragon
force-pushed
the
fix/query-params-patternproperties
branch
2 times, most recently
from
b9b71ef to
ba59cb0
Compare
paragon
force-pushed
the
fix/query-params-patternproperties
branch
from
ba59cb0 to
b88c5be
Compare
ernado
approved these changes
Sep 16, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
When providing
patternPropertiesfor aGETrequest, thequery_param_decoder.DecodeFieldsmethod does not appropriately consider the presence of free-formed fields (i.e.patternPropertiesandadditionalProperties).This PR adjusts the
deepObjecthandling to ensure that this is handled correctly.