Publish OAS 3.0.0 #1283
Merged
Publish OAS 3.0.0 #1283
Conversation
This file contains 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
fixed some tables and language
…dm/operationref # Conflicts: # versions/3.0.md
Captitalise key words, update guidance to rfc8174
strengthen project definition, improve flow
plain language edits
minor edits
minor edits
minor editorial changes
Fix schemas/Error code property in Uber example
Limit parameter content object to one media type object
This attempts to use `document` in its various forms when discussing the artifact (replaces `file` in the most part), though I tried to avoid mixing the file-like instances with the API documentation ones. Some instances have been changed to use `define` (or similar forms), though based on the comments suggesting that both `definition` and `description` are used in common parlance, `description` has not been fully expunged—hopefully this is a reasonable middle ground, but if upon review there is strong support for that, I'll re-submit.
Work by people in the TDC and marketing committee
Fix examples object example and api-with-examples
Ensure all yaml/json examples parse ok
Prefer `description` when referring to an OAS document
Update readme for v3
'#/paths/~12.0~1repositories~1/{username}/get' == '#/paths/<'/2.0/repositories/{username}'.encode()>/get
paths:
/2.0/repositories/{username}:
get:
#1292 Added a missing / separator after the paths in operationRef
rename file Rename 3.0.md to 3.0.0.md
Updated content key descriptions
Update guidelines for v3 and Swagger --> OAS
3.0.0 Release Preparation
|
Great! |
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.
🎉 Publish The OpenAPI Specification 3.0.0 🎉