Uh oh!
There was an error while loading. Please reload this page.
v3.2: Bug fix: deepObject explode default behavior. - #4818
Merged
Conversation
The `explode` field defaults to `false` with `style: deepObject`, but the behavior of that combination is undefined in 3.0 and 3.1. For 3.2, define it to behave the same as `style: deepObject, explode: true`, which maintains compatibility (by defining previously undefined behavior rather than changing the defined default value) and produces intuitive results.
karenetheridge
previously approved these changes
Aug 3, 2025
Uh oh!
There was an error while loading. Please reload this page.
handrews
dismissed stale reviews from mikekistler and karenetheridge
via
August 7, 2025 18:58
533c6d3ralfhandl
approved these changes
Aug 8, 2025
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
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
5 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.
Fixes#4816.
The
explodefield defaults tofalsewithstyle: deepObject, but the behavior of that combination is undefined in 3.0 and 3.1.For 3.2, define it to behave the same as
style: deepObject, explode: true, which maintains compatibility (by defining previously undefined behavior rather than changing the defined default value) and produces intuitive results.Note that there is no need to update the Header Object because it does not allow
style: deepObject.