v3.1-dev: sync with dev #70
Merged
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
![ralfhandl-repo-access-token[bot]](https://avatars.githubusercontent.com/u/951576?s=80&v=4){kind=small}
v3.2: Support all common XML node types (element, attribute, text, cdata)
v3.2: Strengthen generic data types to a SHOULD
Co-authored-by: Ralf Handl <[email protected]>
Since we are testing with a placeholder, we need to match the placeholder. This will unfortunately need to be different on each new release line branch, so let's separate this test case into its own file.
3.2: try to fix automation for jsonSchemaDialect.yaml
We require `content` but failed to require it to be non-empty, even though a request body without a body does not make any sense.
3.2 merge dev
v3.2: (port of OAI#4614) Clarify that Request Body Objects need a body
v3.2-dev: update from dev
These media types solve our long-standing problems with modeling HTTP Link headers. We do not need to define anything beyond noting how to use them media types in a Media Type Ojbect.
We allow multiple `contentType` values in the Encoding Object, but do not provide any guidance on how to determine which to use when performing the encoding. This adds such guidance.
This adds the Media Type Object's encoding field to the Encoding Object to support nested multipart documents. It only requires one level of nesting, but allows implementations to support more.
v3.2: improve wording for servers object and url
v3.2-dev: update from dev
We don't really need the stuff about character encodings, as it was there because I was confused about something else. Also minimize the explanation of the change.
Co-authored-by: Lorna Jane Mitchell <[email protected]>
v3.2-dev: update from dev
Examples at different levels serve different purposes, and it is not clear what is meant by "overriding." Removing this will allow tools to determine the most appropriate example(s) to show in a given context.
v3.2: Add support for application/linkset[+json]
Co-authored-by: Ralf Handl <[email protected]>
updates for the "xml" and "example" keywords
…ments fix character terminology in ABNF comments
…nants v3.2 schema edits
Official 3.1.2 release branch
Official 3.2.0 release branch
main: Fix broken links in 3.2.0.md
main: adjust reviewers in respec workflow
- create sync branch from dev - merge main into sync branch - restore src/* and tests/* from dev - commit & push - create PR if necessary
dev: sync with main
- create sync branch from dev - merge main into sync branch - restore src/* and tests/* from dev - commit & push - create PR if necessary
Align with sync-main-to-dev.yaml
dev: sync with main
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
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.
Merge relevant changes from
devintov3.1-dev.