Skip to content

Fix decoding of unrecognized visual instruction component types#394

Merged
1ec5 merged 1 commit intomasterfrom
1ec5-visualcomponent-type-none
Dec 21, 2019
Merged

Fix decoding of unrecognized visual instruction component types#394
1ec5 merged 1 commit intomasterfrom
1ec5-visualcomponent-type-none

Conversation

@1ec5
Copy link
Contributor

@1ec5 1ec5 commented Dec 20, 2019

Fixed an issue where an unrecognized type of visual instruction component would cause the component to fail to decode. Instead, treat the component as a text component, as specified in the Directions API documentation.

The regression was introduced in #382. This PR reintroduces pretty much the same code that we had before:

https://github.com/mapbox/MapboxDirections.swift/blob/65857d14080afa1e5463e0dbadd9dec23e66a6f3/Sources/MapboxDirections/MBVisualInstructionComponent.swift#L56

/cc @mapbox/navigation-ios @danpaz

Fixed an issue where an unrecognized type of visual instruction component would cause the component to fail to decode. Instead, treat the component as a text component, as specified in the Directions API documentation.
@1ec5 1ec5 added the bug label Dec 20, 2019
@1ec5 1ec5 added this to the v1.0 milestone Dec 20, 2019
@1ec5 1ec5 requested a review from JThramer December 20, 2019 20:51
@1ec5 1ec5 self-assigned this Dec 20, 2019
@1ec5 1ec5 merged commit ff9997d into master Dec 21, 2019
@1ec5 1ec5 deleted the 1ec5-visualcomponent-type-none branch December 21, 2019 02:10
@1ec5 1ec5 modified the milestones: v1.0.0, v0.31.0 (v0.40) Apr 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant