Update guidelines for v3 and Swagger --> OAS #1280
Conversation
guidelines/v2.0/EXTENSIONS.md
Outdated
| * within the [responses object](https://github.com/swagger-api/swagger-spec/blob/master/versions/2.0.md#responses-object) | ||
| * within the [tag object](https://github.com/swagger-api/swagger-spec/blob/master/versions/2.0.md#tag-object) | ||
| * within the [security-scheme object](https://github.com/swagger-api/swagger-spec/blob/master/versions/2.0.md#security-scheme-object) | ||
| * within the [info object](https://github.com/OAI/OpenAPI-Specification/blob/OpenAPI.next/versions/2.0.md#info-object) |
There was a problem hiding this comment.
Link to master instead of OpenAPI.next.
There was a problem hiding this comment.
should not need to include the branch - just use relative links instead of absolute links, such as :
within the [info object](2.0.md#info-object)
There was a problem hiding this comment.
We're the file links to the spec versions which are in a different folder, @DavidBiesack , but maybe an absolute path will work (/versions/2.0.md#info-object)?
There was a problem hiding this comment.
Fixed - changed them to links like /versions/2.0.md#info-object and that seems to work.
guidelines/v2.0/EXTENSIONS.md
Outdated
| # OpenAPI Extensions | ||
|
|
||
| The Swagger 2.0 specification allows for custom properties to be added at several places within a Swagger definition, allowing | ||
| The OpenAPI Specification version 2.0 allows for custom properties to be added at several places within an OpenAPI definition, allowing |
|
Please add extensions.md file at the root of the guidelines folder linking to the moved file under the new directory (to avoid link breakage). |
|
Added the EXTENSIONS.md at the root, linking to the one in 2.0. |
3 participants
Create v2.0 folder, move the files there, and update them to reflect OAS wherever that reflects the up to date name of the spec.