This makes it possible to bias your searches to look in a certain area (e.g. your current location), instead of searching globally. This generally improves the quality of the results when you want to search in your current area.
The API has been extended to support an optional second parameter when the first argument is a string.
The second argument should be a bounds object with the following layout:
type BoundsType = {
southeast: {
lat: number,
lng: number
},
northeast: {
lat: number,
lng: number
}
}
Hi, first of all thanks for this lib 👍 👍
This PR adds support for the
bounds
parameter for address based searches. https://developers.google.com/maps/documentation/geocoding/intro?hl=pt#ViewportsThis makes it possible to bias your searches to look in a certain area (e.g. your current location), instead of searching globally. This generally improves the quality of the results when you want to search in your current area.
The API has been extended to support an optional second parameter when the first argument is a string.
The second argument should be a bounds object with the following layout:
Usage of extended API:
Works like a charm. Let me know if you have any questions.
cheers, Hein