feat: remove override.fetch.explode option (BREAKING CHANGE)
#2481
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
soartec-lab
added
enhancement
melloware
approved these changes
Oct 26, 2025
zhu-hong
pushed a commit
to zhu-hong/orval
that referenced
this pull request
Oct 29, 2025
…-labs#2481) * feat: remove `override.fetch.explode` option (BREAKING CHANGE) * docs: remove override.fetch.explode documentation
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.
fix #2478
Removed the
override.fetch.explodeoption that was kept only for compatibility.Summary
Removed the
override.fetch.explodeoption.This parameter was maintained solely for backward compatibility. Since compatibility maintenance is no longer required in major versions, it has been removed. Users should now specify
explodedirectly in their OpenAPI specification files.