Add support for Google Places API in <GeoAddressSearch>
#1321
Conversation
This file contains hidden or 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
mdastous-bentley
changed the title
<GeoAddressSearch> Add support for Google services<GeoAddressSearch>
aruniverse
approved these changes
May 28, 2025
aruniverse
reviewed
May 28, 2025
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.
Address provider can now be optionally set to Google, which will make the components consume the Google Places API.
An appropriate Google API key needs to be provided.
IMPORTANT:
You must use a Google base map in order to use the Google address search, this is required by the Google policy. If you switch to another base map, the widget get automatically disabled until you re-enable a Google base map: