-
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
Objective-C removal followups for navigation SDK compatibility #393
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a rerpise of the line comments I left the other day, now that there’s a proper PR to hang the comments off of.
public var error: String? | ||
public let uuid: String? | ||
public let routes: [Route]? | ||
public let waypoints: [Waypoint]? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change requires us to address all of #391. Are you sure we should do so before integrating the navigation SDK with the first round of Swifitification in this library?
38ee296
to
895971c
Compare
Also reshuffled RouteStep a bit.
Also made approachIndex and outletIndex optional instead of setting them to −1 at the route endpoints.
Splitting an empty string results in an array containing an empty string.
895971c
to
e556d6e
Compare
This PR aims to fix some loose ends found while working on mapbox/mapbox-navigation-ios#2275. It is a work-in-progress.
/cc @mapbox/navigation-ios