-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
[Maps] Review request for Microsoft.Maps/Microsoft.Maps to add version preview/2.0 #14694
Conversation
This reverts commit 85370d9b6b3ad0ae615d1931aa7a5eec39957b30.
This reverts commit be16d4423be319cc4b7a957abe977aced26e0fa5.
This reverts commit 0458cbc9489ba8cc05a575517b35001fa4c4a7e8.
…ey from examples.
@tjprescott this PR is a modification of current Swagger for all 17 Maps services so that the code is actually generated and AutoRest does not complain about the model anymore. The #14625 just adds a new 2.1 version of the Render service. |
"MapTileResultv2": { | ||
"description": "The tile returned from a successful API call.", | ||
"type": "string", | ||
"format": "binary", | ||
"readOnly": true | ||
} |
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.
This definition is still being referenced above. Should it be kept?
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.
You mean MapTileResultv2? It's not referenced anymore since 200 response definition was changed to describe a file as a response.
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.
I see. I thought the response still referenced this as a schema. My mistake.
…eturn 200 directly (202 instead) the TS codegen takes 200 definition for the response type, so it is needed to deserialize.
…ue to invalid deserialization of base class properties only
The direction of the changes moved to #14871 |
This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
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.