You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#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.
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:
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:
#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: