Rely on Turf to encode and decode GeoJSON LineStrings #638
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1ec5
force-pushed
the
1ec5-polylinestring-encode-type
branch
from
40ee15f to
3c6bcc3
Compare
1ec5
added
the
op-ex
Udumft
approved these changes
Dec 21, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Removed
PolyLineString’s custom LineString encoding and decoding implementation in favor of Turf’s built-in implementation. This fixes an issue wherePolyLineStringencoded a GeoJSON LineString that was invalid because it was missing thetypeproperty. (As a result, GeoJSON-formatted Directions API responses were becoming malformed when round-tripped back to JSON.) It will also take advantage of the foreign member support added in mapbox/turf-swift#175 once that gets released./cc @mapbox/navigation-ios