how to prevent submit from setting the viewport to the result coords? about react-map-gl-geocoder

[SamSamskies]

@mark-rodgers just published v1.8.0. Now you should be able to just do this and the weird behavior of the viewport updating even when passing a noop to onViewportChange is gone. I may not have to make a version 2 after all. 😄

handleGeocoderResult = result => {
  this.setState({
    searchLngLat: result.result.center
  });
};

<Geocoder
  mapRef={this.mapRef}
  onResult={this.handleGeocoderResult}
  mapboxApiAccessToken={"***"}/>

Let me know if you have any other problems.

[SamSamskies]

Hi @mark-rodgers, sorry, but I don't think that's possible. You'll probably need to build a custom component to do that using the Mapbox geocoding API. https://docs.mapbox.com/api/search/#geocoding

You could prob borrow a lot of code from https://github.com/mapbox/mapbox-gl-geocoder/blob/master/lib/index.js

[easherma]

@mark-rodgers if you can access all the config settings from the geocoder-api, you can set flyTo to be false, which should do what you are looking for, no?
https://github.com/mapbox/mapbox-gl-geocoder/blob/master/API.md

[SamSamskies]

@easherma you can actually pass flyTo down as a prop, but unfortunately that only prevents the animation from happening. It will still go to the location that is searched for.

Ideally, this component shouldn't move if you pass in a noop as the onViewportChange prop value. However, since I'm using the mapbox-gl-geocoder object to do most of the heavy lifting, I don't think that's possible. If I ever get around to writing a version 2 of this component, I plan to remove the mapbox-gl-geocoder dependency. Then I'd be able to get rid of this unexpected behavior.

[SamSamskies]

@easherma you're actually right. I misunderstood how flyTo works. Sorry, I'm a dummy.

@mark-rodgers You have to set flyTo to false and also pass in a noop to onViewportChange.

handleGeocoderResult = result => {
  this.setState({
    searchLngLat: result.result.center
  });
};

<Geocoder
  mapRef={this.mapRef}
  onViewportChange={() => {}}
  flyTo={false}
  onResult={this.handleGeocoderResult}
  mapboxApiAccessToken={"***"}/>

[SamSamskies]

@mark-rodgers I'm going to remove the flyTo param as that should always be false. This is a bug in my code due to my misunderstanding of what the flyTo option does. onViewportChange should be the only way to update the viewport. I'll also default onViewportChange to a noop. That way you won't even need to provide those props.

[mark-rodgers]

Awesome! I’ll checkout the latest release soon, I’m sure this update will be useful to many!

[easherma]

Yay! Glad I could help clarify.

On Thu, Apr 11, 2019 at 12:44 AM Mark Rodgers ***@***.***> wrote: Closed #31 <#31>. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#31 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AKDTT4nIoHGajOpOqrUV6RFjn64LCiKdks5vfsuwgaJpZM4cfkgt> .

-- Eric Sherman 224-402-0004