Add json examples for v3 specification #1357
Closed
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
| "info": { | ||
| "version": "1.0.0", | ||
| "title": "Swagger Petstore", | ||
| "description": "A sample API that uses a petstore as an example to demonstrate features in the swagger-2.0 specification", |
There was a problem hiding this comment.
swagger-2.0 specification should be changed to OpenAPI 3.0 specification as per PR #1373
|
Thanks for the PR. We do think having the JSON examples are valuable, however, we don't want to add the additional maintenance burden to keep them up to date. We plan on adding tooling to the repo to generate these JSON examples. However, we can't merge this into master because the spec has some links to the 3.0 examples. We will do this work in the 3.0.1 release. See #1385 |
Closed
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.
No description provided.