On result handler about react-map-gl-geocoder HOT 9 CLOSED

There's not an easy way to do this right now. I'll try and work on adding the ability to pass these in as props this weekend.

from react-map-gl-geocoder.

Thanks so much!

from react-map-gl-geocoder.

I added props for onResults and onResult in the latest version. README is updated with all available props. Let me know if you have any problems.

from react-map-gl-geocoder.

Am I correct in understanding that all I have to do is pass a function to the onResult prop to achieve the same result as this example?

I tried this and nothing got printed after searching + selecting a result:

_onGeocoderResult = (results) => {
  console.log(results);
}
// ... a bunch of code and ReactMapGL wrapper 
<Geocoder mapRef={this.mapRef}
  onResult={this._onGeocoderResult}
  onViewportChange={this._handleGeocoderViewportChange}
  mapboxApiAccessToken={config.MAPBOX_PUBLIC_TOKEN} />

Again, thanks so much for your help!

from react-map-gl-geocoder.

That should work. Could you verify that you're using v1.4.5?

See example here: https://codesandbox.io/s/0vpoxn0n9l

I just noticed there's an existing bug with mapbox-gl-geocoder that causes onResult to fire twice. mapbox/mapbox-gl-geocoder#99.

from react-map-gl-geocoder.

I'll try removing my dependencies and re-updating!

from react-map-gl-geocoder.

Does the example work for you? If it doesn't, let me know what your search query is.

from react-map-gl-geocoder.

It worked! I just had to remove my node_modules folder and reinstall. :) Thanks so much Sam!

from react-map-gl-geocoder.

No problem. Let me know if that bug causing the event to fire twice is a problem for you. I can try and help them fix the bug or figure out a workaround if it is.

from react-map-gl-geocoder.