feat: Per-Request Language Option for Map Queries #48763
Conversation
github-actions
bot
added
Community Contribution
|
Thank you for your contribution @PlaySkyHD! We will review the pull request and get back to you soon. |
|
@microsoft-github-policy-service agree |
|
API change check APIView has identified API level changes in this PR and created following API reviews. |
|
What does the pipeline step "Verify Generated Code" do? How can I fix it? |
|
Hi @PlaySkyHD. Thank you for your interest in helping to improve the Azure SDK experience and for your contribution. We've noticed that there hasn't been recent engagement on this pull request. If this is still an active work stream, please let us know by pushing some changes or leaving a comment. Otherwise, we'll close this out in 7 days. |
github-actions
bot
added
the
no-recent-activity
|
Hi @PlaySkyHD , thanks for contributing. We're aware of this issue and we'll provide setting language in each API calls in our next release. |
github-actions
bot
removed
the
no-recent-activity
|
Hey @dubiety, |
Changes
Added support for setting the language per request for the following queries:
The existing language setting at the MapsSearchClient level remains functional. If no language is provided via request options, the default value from MapsSearchClient is used.
Background
This change was introduced to support a multi-user application, where each user can configure their preferred language. Previously, language settings were only available at the MapsSearchClient level, requiring separate instances per user. With this update, we can specify the language dynamically per request without needing to create multiple client instances.