-
Notifications
You must be signed in to change notification settings - Fork 359
Update to latest version of the swagger #555
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
The swagger file has a new version
@seilorjunior : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
Learn Build status updates of commit d18bcc9: ✅ Validation status: passed
For more details, please refer to the build report. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
Updates the Speech service Swagger specification documentation to reference the latest version 3.2 instead of the previous version 3.1.
- Updated the URL in the Swagger specification link to point to version 3.2
- Updated the documentation text to reflect the new version
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
## Generating code from the Swagger specification | ||
|
||
The [Swagger specification](https://github.com/Azure/azure-rest-api-specs/blob/master/specification/cognitiveservices/data-plane/Speech/SpeechToText/stable/v3.1/speechtotext.json) has options that allow you to quickly test for various paths. However, sometimes it's desirable to generate code for all paths, creating a single library of calls that you can base future solutions on. Let's take a look at the process to generate a Python library for the Speech to text REST API version 3.1. | ||
The [Swagger specification](https://github.com/Azure/azure-rest-api-specs/blob/master/specification/cognitiveservices/data-plane/Speech/SpeechToText/stable/v3.2/speechtotext.json) has options that allow you to quickly test for various paths. However, sometimes it's desirable to generate code for all paths, creating a single library of calls that you can base future solutions on. Let's take a look at the process to generate a Python library for the Speech to text REST API version 3.1. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The text mentions generating a Python library for 'Speech to text REST API version 3.1' but the URL now points to v3.2. This creates inconsistency in the documentation. The version reference should be updated to 3.2 to match the updated URL.
Copilot uses AI. Check for mistakes.
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
The swagger file has a new version (3.2)