-
Notifications
You must be signed in to change notification settings - Fork 16
Open
Labels
triage meI really want to be triaged.I really want to be triaged.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Description
Environment details
- Specify the API at the beginning of the title (for example, "Places: ...")
- OS type and version: ChromeOS / Linux
- Library version and other environment information: @googlemaps/extended-component-library: 0.6.13
When running the autocomplete widget, I get the following console warning:
As of March 1st, 2025, google.maps.places.Autocomplete is not available to new customers. Please use google.maps.places.PlaceAutocompleteElement instead. At this time, google.maps.places.Autocomplete is not scheduled to be discontinued, but google.maps.places.PlaceAutocompleteElement is recommended over google.maps.places.Autocomplete. While google.maps.places.Autocomplete will continue to receive bug fixes for any major regressions, existing bugs in google.maps.places.Autocomplete will not be addressed. At least 12 months notice will be given before support is discontinued. Please see https://developers.google.com/maps/legacy for additional details and https://developers.google.com/maps/documentation/javascript/places-migration-overview for the migration guide.
A simple <PlacePicker>
is enough to cause this warning:
<PlacePicker id={id} placeholder={defaultValue} onPlaceChange={handleChange} />
Will this library be updated to support the new underlying library mentioned in the migration guide?
kiraahmad, mcastilloy2k, beetlegius-somos, zekgyn, marucjmar and 7 more
Metadata
Metadata
Assignees
Labels
triage meI really want to be triaged.I really want to be triaged.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.