Uh oh!
There was an error while loading. Please reload this page.
v3.2 schema edits - #4957
Conversation
- "in" is always required for "parameter" - "type" is required for "security-scheme"
b1376fa to
1b20dbcCompare
ralfhandl
left a comment
There was a problem hiding this comment.
Test case pass/path_item_servers_parameters.yaml fails with these schema changes.
Uh oh!
There was an error while loading. Please reload this page.
1b20dbc to
39cca69Comparekarenetheridge
commented
Sep 15, 2025
Thanks, I've fixed the test failure. |
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
karenetheridge
commented
Sep 15, 2025
|
0a03cfc to
2d201d6Comparekarenetheridge
commented
Sep 16, 2025
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
2463bd0Comparekarenetheridge
commented
Sep 18, 2025
I found one more thing to add, but I'll make a new PR for that. |
Uh oh!
There was an error while loading. Please reload this page.
Several schema improvements for v3.2. One of them MUST be in the release, as it allows for the use of
in: cookie, style: cookiethat was prohibited before.I will backport to v3.1 the things that are relevant there.