Maps search 2025 01 01 #32091
Merged
Maps search 2025 01 01 #32091
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
Next Steps to Merge✅ All automated merging requirements have been met! To get your PR merged, see aka.ms/azsdk/specreview/merge. |
|
PR validation pipeline restarted successfully. If there is ApiView generated, it will be updated in this comment. |
github-actions
bot
added
the
brownfield
|
API change check APIView has identified API level changes in this PR and created following API reviews. |
gigigoo0
added
the
PublishToCustomers
gigigoo0
requested review from
DominikMe and
weidongxu-microsoft
and removed request for
a team
dubiety
approved these changes
Jan 10, 2025
mikekistler
reviewed
Jan 13, 2025
mikekistler
reviewed
Jan 13, 2025
|
Do we have a review schedule for this stable api-version? I didn't find it in links/comments within this PR. (wanted to find what was already be discussed, what's new in this version, etc.) |
Requested an offline review on teams channel since we're only adding new response properties. |
weidongxu-microsoft
approved these changes
Jan 15, 2025
mikekistler
added
the
offline-review-requested
mikekistler
added
the
APIStewardshipBoard-SignedOff
pbrasil
approved these changes
Jan 17, 2025
gigigoo0
force-pushed
the
maps-search-2025-01-01
branch
from
454d3c0 to
249ecd2
Compare
markcowl
pushed a commit
to markcowl/azure-rest-api-specs
that referenced
this pull request
Feb 6, 2025
* base commit * Add version 2025-01-01 * update readme * update cspell config
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.
Data Plane API Specification Update Pull Request
Tip
Overwhelmed by all this guidance? See the
Getting helpsection at the bottom of this PR description.PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.
API Info: The Basics
Most of the information about your service should be captured in the issue that serves as your API Spec engagement record.
Is this review for (select one):
Change Scope
This section will help us focus on the specific parts of your API that are new or have been modified.
Please share a link to the design document for the new APIs, a link to the previous API Spec document (if applicable), and the root paths that have been updated.
/geocode,/geocode:batch,/reverseGeocode,/reverseGeocode:batchViewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the
Generated ApiViewcomment added to this PR. You can use ApiView to show API versions diff.Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
Swagger-Suppression-Process
to get approval.