You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the suggestions provided by the Google Places API Web Service have a wide breadth in the types of suggestions (i.e. an establishment, city/locality, specific address, etc.) returned when the user first starts searching for a place. The set of returned suggestions may also not be geospatially tight ("close to each other"). As the users search becomes more specific the types of suggestions returned start to narrow as well as tighten geospatially around each other. This is due to the fact that the request made to the Google Places API Web Service is unassuming and simply provides the users search input. This doesn't provide flexibility for meeting the use cases of those that consume <MUIPlacesAutocomplete>.
Consumers of <MUIPlacesAutocomplete> may have specific use cases in mind for their customers where they may want to:
Specify (i.e. narrow) the types of suggestions returned by the Google Places API Web Service
Bias/restrict the suggestions returned by the Google Places API Web Service to a specific area
This is a feature request to allow for more control over the suggestions returned by the Google Places API Web Service.
The text was updated successfully, but these errors were encountered:
This commit exposes a new prop on <MUIPlacesAutocomplete> named
'createAutocompleteRequest'. Consumers of <MUIPlacesAutocomplete> may
provide a function to the 'createAutocompleteRequest' prop that returns
an object that is used as the request to the Google Places API Web
Service when querying for suggestions. This object may be customized
(per Google API docs) to allow for greater control over what suggestions
are returned to us (the user).
modified: README.md
modified: src/MUIPlacesAutocomplete.jsx
Currently the suggestions provided by the Google Places API Web Service have a wide breadth in the types of suggestions (i.e. an establishment, city/locality, specific address, etc.) returned when the user first starts searching for a place. The set of returned suggestions may also not be geospatially tight ("close to each other"). As the users search becomes more specific the types of suggestions returned start to narrow as well as tighten geospatially around each other. This is due to the fact that the request made to the Google Places API Web Service is unassuming and simply provides the users search input. This doesn't provide flexibility for meeting the use cases of those that consume
<MUIPlacesAutocomplete>
.Consumers of
<MUIPlacesAutocomplete>
may have specific use cases in mind for their customers where they may want to:This is a feature request to allow for more control over the suggestions returned by the Google Places API Web Service.
The text was updated successfully, but these errors were encountered: