Skip to content
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

Merged
merged 79 commits into from
Feb 22, 2021

Conversation

alexhcheng
Copy link
Contributor

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.

  1. What's the purpose of the update?
    • new service onboarding
    • new API version
    • update existing version for new feature
    • update existing version to fix swagger quality issue in s360
    • Other, please clarify
  2. When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet.
  3. When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
  4. If it's an update to existing version, please select SDKs of specific language and CLIs that require refresh after swagger is published.
    • SDK of .NET (need service team to ensure code readiness)
    • SDK of Python
    • SDK of Java
    • SDK of Js
    • SDK of Go
    • PowerShell
    • CLI
    • Terraform
    • No, no need to refresh for updates in this PR

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.

    • Adding new API(s)
    • Adding a new API version
    • Adding a new service
  • 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.

  • Removing API(s) in stable version
  • Removing properties in stable version
  • Removing API version(s) in stable version
  • Updating API in stable or public preview version with Breaking Change Validation errors
  • Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

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.

@azure-pipelines
Copy link

Azure Pipelines successfully started running 2 pipeline(s).

@openapi-workflow-bot
Copy link

Hi @alexhcheng, Your PR has some issues. Please fix the CI sequentially by following the order of Avocado, semantic validation, model validation, breaking change, lintDiff.

TaskHow to fixPrioritySupport (Microsoft alias)
AvocadoFix-AvocadoHighruowan
Semantic validationFix-SemanticValidation-ErrorHighraychen, jianyxi
Model validationFix-ModelValidation-ErrorHighraychen,jianyxi
LintDiffFix-LintDiffhighjianyxi, ruoxuan
If you need further help, please feedback via swagger feedback."

Copy link
Member

@maririos maririos left a 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": [
Copy link
Member

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

@maririos
Copy link
Member

Question about the location of the files. They are currently under TranslatorText although this is the DocumentTranslator service. Will that be a concern? like should it be in it's own folder?
Or organize it like Translator/TextTranslator and Translator/DocumentTranslator?

@jhendrixMSFT
Copy link
Member

@alexhcheng does anybody from your team need to review this? Looks good from my side.

@alexhcheng
Copy link
Contributor Author

@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

@jhendrixMSFT jhendrixMSFT merged commit a23007d into Azure:master Feb 22, 2021
mkarmark pushed a commit to mkarmark/azure-rest-api-specs that referenced this pull request Jul 21, 2021
…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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Approved-BreakingChange DO NOT USE! OBSOLETE label. See https://github.com/Azure/azure-sdk-tools/issues/6374
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants