-
Notifications
You must be signed in to change notification settings - Fork 90
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
Remove DirectionsResult.routeIdentifier property #452
Comments
1ec5
added
backwards incompatible
changes that break backwards compatibility of public API
op-ex
Refactoring, Tech Debt or any other operational excellence work.
labels
Sep 2, 2020
Merged
The postprocessing step imbues each route with its surrounding response’s UUID, so the values do match, even if it’s a code smell to use this vestigial property:
|
2 tasks
1ec5
removed
the
backwards incompatible
changes that break backwards compatibility of public API
label
Oct 2, 2020
1ec5
modified the milestones:
duck (android-v1.4.0 / ios-v1.2.0),
e (android-v1.5.0 / ios-v1.3.0)
Jan 22, 2021
Closed by #562 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
#406 moved the UUID from each individual Route to the RouteResponse, aligning with the Directions API. However, it looks like it kept around a vestigial
DirectionsResult.routeIdentifier
property. We should remove this property. However, if we need to defer this work past v1.0, then we should instead deprecate the property and wait until v2.0 to remove it.mapbox-directions-swift/Sources/MapboxDirections/DirectionsResult.swift
Lines 153 to 158 in 8438c7a
mapbox-directions-swift/Sources/MapboxDirections/DirectionsResult.swift
Line 59 in 8438c7a
By design, this property is no longer set to anything, but there are still unit tests that assert that it is set to a meaningful value. These tests pass because we haven’t updated the test fixtures./cc @mapbox/navigation-ios
The text was updated successfully, but these errors were encountered: