Minh Nguyễn

The scope of this feature would be a minimal compatibility layer; I don't think it would be worth porting all of the Directions API's logic directly to Swift. 😉 @freenerd...

Copied from https://github.com/mapbox/mapbox-navigation-ios/issues/46#issuecomment-296352234: > Since MapboxDirections.swift currently only knows how to issue requests to the Mapbox Directions API, you’ll need to write your own code to construct the request URL...

Some tests are failing because the test fixtures need to updated. They were generated back before the Directions and Map Matching APIs started returning `distance` as part of each snapped...

A major problem with converting Waypoint to a struct is that a given waypoint appears in multiple places in the response. The developer would potentially expect that changing the name...

Both these behaviors would be dependent on the routing engine. /cc @mapbox/navigation-api

The [iOS navigation SDK](https://github.com/mapbox/mapbox-navigation-ios/) supports Valhalla for offline routing via the MapboxNavigationNative framework. At the moment, MapboxDirections.swift only supports a Valhalla server endpoint if that endpoint translates the requests and...

#393 added initializers for Route, RouteLeg, and RouteStep that you can use as a workaround to transform raw Valhalla responses to type-safe model objects.

watchOS doesn’t support XCTest, but [XCTest-watchOS](https://github.com/dfed/XCTest-watchOS/) is a third-party implementation that supports both Carthage and SPM.

These API response properties are now [documented here](https://www.mapbox.com/api-documentation/#route-object).

I’d check first if the code they provided results in a NavigationMatchOptions and NavigationRouteOptions that has `routeShapeResolution` set to `full` (it should).