Dummy PR for merging 3.1.1 into main #4076
Closed
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
…re also valid for style=simple
This is a more natural grouping of similar types, making the data much easier to read.
…e-style the chart in section 4.8.12.4 shows that primitive and object types are also valid for style=simple
…v3.1.1 switch the order of these styles in the tables
…ct-extra-params extra keywords in the reference object are permitted (v3.1.1)
Co-authored-by: Ralf Handl <[email protected]>
Remove "redact" from wording, leaving only "obscure". Co-authored-by: Rob Ede <[email protected]>
Co-authored-by: Ralf Handl <[email protected]>
Co-authored-by: Ralf Handl <[email protected]>
merging per today's TDC call
…d-composition merging after discussion on the TDC call today
* Sync validate-markdown workflow with main (3.1.1) * Match latest environment from main
Generalize description of password data type
…ples-v3.1.1 whitespace and quoting fixes in json and yaml examples (v3.1.1)
Co-authored-by: Adam Altman <[email protected]>
Co-authored-by: Mike Kistler <[email protected]>
…ts-3.1.1 small typo fix
3.1.1 discriminator improvements
Move Mutual TLS example from 3.1.0 to 3.1.1 to prepare for patch release
Co-authored-by: Mike Kistler <[email protected]>
Co-authored-by: Mike Kistler <[email protected]>
markdownlint for 3.1.1.md
…mt restrictions Clarifies that OAS data modeling is based on the types in the `type` validation keyword, but JSON Schema keywords and formats apply (or not) based on the JSON instance data model, which does not include integers. Co-authored-by: Mike Kistler <[email protected]>
Clarify data model types and formats
Define capital-O "Object" to make it clear why it is only occasionally capitalized. Use lowercase "with" in titles consistently (it was more common than capitalized "With". This is one of those rules that is different depending on whose style guide you use- about half the major guides say always lowercase, the other say always captial. We were using lowercase more often. Also, fix "Working with Examples" to be a subsection of the Example Object as otherwise it breaks the pattern of all of the headings of its level being Object definitions. I remember messing with this a lot when I first posted that PR and either I just missed this or I had some reason I have now forgotten to do it this way.
These got lower-cased because I did not explain in the text that the capital is significant. The previous commit adds the explanation (ported from 3.0.4) and this fixes the 3.1.1-specific occurrences.
"Object" definition, etc. (3.1.1 port of OAI#3050)
…-as-message-body 3.1.1: example for "raw JSON" as message body
3.1.1: tables cleanup
…urity 3.1.1: absent, empty, or incomplete security list
3.1.1: port the undisputed parts of OAI#2140
|
Closing this dummy PR |
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.
This is a dummy PR showing the differences between
mainandv3.1.1-devafter mergingDo not merge!
Once #4074 is merged, this will be replaced with a "Release PR" for merging
v3.1.1-devintomain.