Update documentation links from referencing 3.0.2 to 3.1.0 #118
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
kdipippo
changed the title
kdipippo
commented
Feb 27, 2024
| @@ -31,7 +31,7 @@ In addition, Redocly recommends placing path parameters within `{}` curly braces | |||
|
|
|||
| * Quickly see a list of all paths. Many people think in terms of the "number" of "endpoints" (paths), and not the "number" of "operations" (paths * http methods). | |||
|
|
|||
| * Only the "file-per-path" option is semantically correct with the OpenAPI Specification 3.0.2. However, Redocly's openapi-cli will build valid bundles for any of the other options too. | |||
There was a problem hiding this comment.
maybe this line is actually something only with 3.0.2 and not with 3.1.0?
|
Apologies! I accidentally closed this PR when cleaning up my GitHub repos thinking this was properly detached. The work done here still applies. |
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.
What/Why/How?
The base spec in this repo was already updated to 3.1.0:
openapi-starter/openapi/openapi.yaml
Line 1 in 2bd7622
The results of
npm testalready validate that this is a correctly formed 3.1.0 spec (the only flag is on the server URL beingexample.com). These links just needed to be updated to accurately reflect the version available in this template repo. The headers on those links also needed to be updated to what the new spec has them listed as.Here are all the new links:
Reference
#116
Testing
These changes are just updates to links in Markdown files.