[cognitive services][machine translation][document batch translator api] Update documentation, support new formats & add storage field to glossaries #12576
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
|
Hi, @FadyEssam Thanks for your PR. I am workflow bot for review process. Here are some small tips. Any feedback about review process or workflow bot, pls contact swagger and tools team. vsswagger@microsoft.com |
Swagger Validation Report
|
Swagger Generation Artifacts
|
ghost
added
the
customer-reported
|
Thank you for your contribution FadyEssam! We will review the pull request and get back to you soon. |
anuchandy
reviewed
Jan 26, 2021
| @@ -862,6 +862,9 @@ | |||
| "description": "Version", | |||
| "type": "string", | |||
| "example": "2.0" | |||
| }, | |||
| "storageSource": { | |||
| "$ref": "#/definitions/StorageSource" | |||
There was a problem hiding this comment.
Is this addition of new property is intentional? I see the description says PR is about doc update, so just want to make sure addition of this property is not by error.
There was a problem hiding this comment.
or this property is to enable the file formats?
There was a problem hiding this comment.
yes this is an intentional property, but it is completely backward compatible (this property has a default value keeping the same behavior)
There was a problem hiding this comment.
updated the PR title
FadyEssam
changed the title
anuchandy
approved these changes
Jan 26, 2021
This was referenced Jan 26, 2021
mkarmark
pushed a commit
to mkarmark/azure-rest-api-specs
that referenced
this pull request
Jul 21, 2021
…pi] Update documentation, support new formats & add storage field to glossaries (Azure#12576) * Update documentation and allow storage type for glossaries * unescape unicode * add new lines at end of files * add new lines at end of files * run prettier * run prettier Co-authored-by: Fady Essam <faanis@microsoft.com>
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.
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Changelog
Please ensure to add changelog with this PR by answering the following questions.
We are going to public preview in start of Feb/2021 so we are deploying latest features to prod by the end of Jan/2021
before the end of Jan/2021
Contribution checklist:
If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist
Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.
Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.
If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.