You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
@@ -12,7 +12,7 @@ This repository is the canonical source for REST API specifications for Microsof
## Creating the Swagger Specification for Azure
- This [document](./documentation/creating-swagger.md) will help you understand how AutoRest converts Swagger in to code.
- If you are using **swashbuckle** to generate a swagger spec from your .NET WEB API then please take a look at this [repo](https://github.com/Azure/swashbuckle-resource-provider).
- Swagger spec for every api-version should be in a serate folder named with the api-version.
- Swagger spec for every api-version should be in a separate folder named with the api-version.
- It is time consuming to review the file line by line for every api-version. When you are creating the swagger spec for the new api-version, please copy the swagger spec from the previous version in to the new api-versioned folder and commit it. After that overwrite it with the changes for the new api-version. This makes it easy for us to review the changes.
