-
Notifications
You must be signed in to change notification settings - Fork 181
version flag for MapboxGeocoder #485
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
ee73618 to
63ec2e7
Compare
mpothier
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@VladislavMedved Great work, this is really close - just a few small changes
c5a0a4d to
57118b9
Compare
767f979 to
885c3ad
Compare
8460ea5 to
d490057
Compare
|
Be sure to remove the yarn lock |
d490057 to
2320845
Compare
ff9dc23 to
64f3267
Compare
pre-validate reverse coordinates to avoid v6 4xx response fix limit=1 on reverse geocodes when single type set enable multiple reverse results when no types or limit specified fix promise resolution revert package-lock file fix potential problem with address strings for v5 and v6
64f3267 to
9199750
Compare
|
|
Is anyone still working on this? It would be really cool to see API v6 in the geocoder |
|
Pinging once again because it's getting ridiculous. |
|
@MateuszKukiela I recommend checking out the Mapbox Search JS SDK, which is the newer SDK and uses the Geocoding V6 API in its libraries: |
Description
PR adds
version="v5"|"v6"flag to the options ofMapboxGeocoderclass that allows using v6 endpoint instead of default v5 when geocoding.Gl-geocoder in v6 mode can initiate
forwardandreversegeocoding calls