-
Notifications
You must be signed in to change notification settings - Fork 9.1k
v3.2: specification: minor clarifications, markup improvements #4959
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
Merged
ralfhandl
merged 5 commits into
OAI:v3.2-dev
from
karenetheridge:ether/v3.2-spec-markup
Sep 16, 2025
Merged
v3.2: specification: minor clarifications, markup improvements #4959
ralfhandl
merged 5 commits into
OAI:v3.2-dev
from
karenetheridge:ether/v3.2-spec-markup
Sep 16, 2025
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
That is, these are also prohibited: - "query" appearing in the path-item's parameters and "querystring" in the operation's parameters - "querystring" appearing in the path-item's parameters and "query" appearing in the operation's parameters
- Literal style names are now rendered in sans-serif as code - "primitive" is not rendered as code, as it refers to one of string, number, boolean or null, not a literal type name.
This does not change the actual values of the examples, but it's more clear that this is literal data being modelled in the schema.
ralfhandl
previously approved these changes
Sep 15, 2025
mikekistler
previously approved these changes
Sep 16, 2025
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. 👍
259ea07
Resolved conflict due to adjacent line changed by merging @mikekistler Please re-approve |
ralfhandl
approved these changes
Sep 16, 2025
mikekistler
approved these changes
Sep 16, 2025
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.
Reapproving.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
clarify other prohibited combinations of
query
andquerystring
clarify that the styles table is comprehensive: other combinations are prohibited
markup improvement to the styles table
removal of json-like formatting in literal yaml examples of
dataValue
sno schema changes are needed for this pull request