Geocoding fails when searchBounds are already in L.latLngBounds format

Hi 👋

I am building a React app that uses React-leaflet, esri-leaflet-geocoder. Zooming into the map to 12+ and then typing the ESRI geocoder results in the following error with stack trace:

The bounds come in formatted as L.latLngBounds but are transformed with the expectation that they’re latLngs, which results in an empty L.latLngBounds object. A class check for latLngBounds before transforming it/or not would probably do it.

Assuming you don’t want search bounds on the geocode search, this error can be avoided by setting the geocoder option { searchBounds: false } https://github.com/Esri/esri-leaflet-geocoder/pull/115

[fungjj92]

I’m fine with closing this issue since it looks like it is not easily reproduced and we came to a good workaround. Thanks again for your attention!

[jgravois]

I wonder if it makes a difference that I am using react-leaflet.

it doesn’t appear to. i can’t see the problem you reported in the app below and its virtually identical to what you shared in your snippet.

https://github.com/kboul/react-esri-leaflet-geosearch

i’m happy to investigate further, but only with a repro case.