v3.3: Add a global parameters field#5446
Open
handrews wants to merge 1 commit into
Open
Conversation
This just adds the field without any special handling. It is already possible with the Path Item Object's parameters field to specify parameters that don't make sense for all of the operations, and we don't attempt to compensate for it. The only truly new situation is that there is no one path to which path parameters would correspond. I suspect that global path parameters will be rare, and mostly used in a prefix as more powerful analogues of Server Variables.
handrews
marked this pull request as ready for review
July 25, 2026 19:39
handrews
changed the title
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 free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 #5320 : Add global
parametersfield without changing any of the ways in which parameters behave at different levels.This is the simplest expansion, and should support known use cases like universal request headers or cookies.
This feature does not interact productively with
in: querystring, and that should be fine for now. We can add complexity there if and when clear use cases emerge. It is not even entirely clear how common a globalin: queryparameter (which would prevent use ofin: querystringeverywhere) would be.Global path parameters would also be odd, but could be used somewhat like Server Variables. The oddness of them does not seem sufficient reason to forbid them, although I could be persuaded given that they would not be clearly associated with any one path template.