Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Decoded RouteResponse doesn't contain targetCoordinate if it was passed via ResponseOptions. #445

Closed
MaximAlien opened this issue Aug 18, 2020 · 0 comments · Fixed by #446
Closed

Decoded RouteResponse doesn't contain targetCoordinate if it was passed via ResponseOptions. #445

MaximAlien opened this issue Aug 18, 2020 · 0 comments · Fixed by #446
Assignees
@MaximAlien
Labels
bug

Comments

@MaximAlien
Copy link
Contributor

In case if RouteResponse is encoded with targetCoordinate, heading, headingAccuracy, separatesLegs and allowsArrivingOnOppositeSide being set and then decoded all stated properties will not be saved in result object. It is expected that encoded and decoded RouteResponse objects have the same properties except coordinate.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@MaximAlien MaximAlien

Labels
bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Improve route response decoding. mapbox/mapbox-directions-swift
1 participant
@MaximAlien