-
Notifications
You must be signed in to change notification settings - Fork 9.2k
v3.2: Allow allowReserved everywhere #4593
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
The restriction on `allowReserved` make some useful configurations impossible, and do not actually prevent pathological scenarios like path parameter values containing `/`, from occurring. Such pathological scenarios are already possible by using `content` instead of `style`/`explode`/`allowReserved`. Lifting the restriction also makes the handling of this field more consistent.
ralfhandl
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1, just one typo
Co-authored-by: Ralf Handl <[email protected]>
|
I changed the ticky box on required schema changes, given that there are some in this PR. |
lornajane
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No objections, kind of hope that not many people need this though
|
Leaving open for anyone with more concerns to chime in before we merge. |
mikekistler
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. 👍
Looks good to me. |
|
That's a strong triple-approval! I'm merging. |
v3.2: Allow `allowReserved` in the Header Object (left out of PR #4593 by mistake)
Fixes:
;in path parameters outside ofmatrixexpansion)The restriction on
allowReservedmake some useful configurations impossible, and do not actually prevent pathological scenarios like path parameter values containing/, from occurring. Such pathological scenarios are already possible by usingcontentinstead ofstyle/explode/allowReserved.Lifting the restriction also makes the handling of this field more consistent, as it is no longer necessary to keep track of the destination.