Andrew Harvey

That would be upstream in https://github.com/mapbox/mapbox-sdk-js, but still something we'll need to resolve. Is it specific to a browser version? It could be something else in your application is affecting...

I agree, that in light of now the external geocoder feature, localGeocoderOnly is not a good design, at the time it made sense, but since things have evolved more organically...

Depends where Mapbox want to take it, I see goal 1 as being core, but with 2 the danger is you could end up with down the track with a...

Thanks for the PR. My view is per #185 we shouldn't be using debounce at all and instead use throttle. I'd like to see more thought and discussion and ultimately...

when one number is >90 or

Currently if you pass in a `lng,lat` it will reverse geocode since this is how the Mapbox Geocoding API works https://www.mapbox.com/api-documentation/#request-format. Though with some combinations of `limit` and `types` it...

https://github.com/mapbox/mapbox-gl-geocoder/blob/master/example/index.js now contains an example of how to do this. I'm thinking it's probably best to leave this up to the implementor (since now with the localGeocoder option it's very...

The example of how you can implement this in your own implementation is at https://docs.mapbox.com/mapbox-gl-js/example/mapbox-gl-geocoder-accept-coordinates/. This ticket can be used to track doing this out of the box.

#175 included a change to detect lat/lon inputs and provide suggestions from the reverse geocoder. This doesn't include the exact lat/lon so if you want users to be able to...

However "Consequently, setting limit to a higher-than-default value requires specifying exactly one types parameter." mapbox-gl-geocoder sets the limit by default to 5, hence requires exactly one types value. (from https://docs.mapbox.com/api/search/#reverse-geocoding)