-
Notifications
You must be signed in to change notification settings - Fork 9.1k
v3.2 schema edits #4957
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
base: v3.2-dev
Are you sure you want to change the base?
v3.2 schema edits #4957
Conversation
- "in" is always required for "parameter" - "type" is required for "security-scheme"
b1376fa
to
1b20dbc
Compare
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.
Test case pass/path_item_servers_parameters.yaml
fails with these schema changes.
1b20dbc
to
39cca69
Compare
Thanks, I've fixed the test failure. |
|
0a03cfc
to
2d201d6
Compare
I edited the querystring commit to add:
Because of the restrictions appearing in two places (path-item and operation) I created a new definition for |
…, explode, allowReserved are present see OAI#4899
2d201d6
to
2463bd0
Compare
I found one more thing to add, but I'll make a new PR for that. |
Several schema improvements for v3.2. One of them MUST be in the release, as it allows for the use of
in: cookie, style: cookie
that was prohibited before.I will backport to v3.1 the things that are relevant there.