-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
[batch document translation][mt] small changes to swagger's name + new fields in response #12965
Conversation
Azure Pipelines successfully started running 2 pipeline(s). |
...tion/cognitiveservices/data-plane/TranslatorText/preview/v1.0-preview.1/TranslatorBatch.json
Show resolved
Hide resolved
Hi @alexhcheng, Your PR has some issues. Please fix the CI sequentially by following the order of
|
...tion/cognitiveservices/data-plane/TranslatorText/preview/v1.0-preview.1/TranslatorBatch.json
Outdated
Show resolved
Hide resolved
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.
LGTM! Thank you Alex!!
"x-ms-enum": { | ||
"name": "StorageInputType", | ||
"modelAsString": true, | ||
"values": [ |
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.
@iscai-msft curious, is the values array necessary? or can it be omitted so no need to maintain enum
and s-ms-enum
Question about the location of the files. They are currently under |
...tion/cognitiveservices/data-plane/TranslatorText/preview/v1.0-preview.1/TranslatorBatch.json
Show resolved
Hide resolved
@alexhcheng does anybody from your team need to review this? Looks good from my side. |
I just had a sync up with our team, they approve these changes. So we are good to go. @jhendrixMSFT |
This reverts commit 3b0e442.
…w fields in response (Azure#12965) * Merged from master again * updated swagger based on API review feedback * updated post * fix spelling * added x-ms-pageable, x-ms-error-response, x-ms-long-running * fix enum * remove long running operation * bug in sdk go generation * Revert "bug in sdk go generation" This reverts commit 025b875. * remove x-ms-pageable * addressed changes * fix casing for x-ms-parameterized-host * fix endpoint in examples * move everything in the same SDK readme file * change path to v1.0_preview.1 * add input type parameter for folder vs file * Merged from master again * updated swagger based on API review feedback * updated post * fix spelling * added x-ms-pageable, x-ms-error-response, x-ms-long-running * fix enum * remove long running operation * bug in sdk go generation * Revert "bug in sdk go generation" This reverts commit 025b875. * remove x-ms-pageable * addressed changes * fix casing for x-ms-parameterized-host * fix endpoint in examples * move everything in the same SDK readme file * change path to v1.0_preview.1 * Update title of swagger page * update ' * updating formating to formatting * Merged from master again * updated swagger based on API review feedback * updated post * fix spelling * added x-ms-pageable, x-ms-error-response, x-ms-long-running * fix enum * remove long running operation * bug in sdk go generation * Revert "bug in sdk go generation" This reverts commit 025b875. * remove x-ms-pageable * addressed changes * fix casing for x-ms-parameterized-host * fix endpoint in examples * move everything in the same SDK readme file * change path to v1.0_preview.1 * Update title of swagger page * Merged from master again * updated swagger based on API review feedback * updated post * fix spelling * added x-ms-pageable, x-ms-error-response, x-ms-long-running * fix enum * remove long running operation * bug in sdk go generation * Revert "bug in sdk go generation" This reverts commit 025b875. * remove x-ms-pageable * addressed changes * fix casing for x-ms-parameterized-host * fix endpoint in examples * move everything in the same SDK readme file * change path to v1.0_preview.1 * update ' * updating formating to formatting * update swagger changes * fix ' * added x-ms-enum * fix x-ms-enum, added a few more xmsextensions, remove go generation for preview * fix examples and error code * add jsonignore to internalcode * fix quotes * modelasstring = true * update x-ms-enum name * Revert "update x-ms-enum name" This reverts commit 3b0e442.
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.
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 Breaking Change 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.