Releases: mapbox/mapbox-directions-swift
Releases · mapbox/mapbox-directions-swift
v0.27.0
- If a
RouteOptions
object has exceptionally many waypoints or if many of the waypoint have very long names,Directions.calculate(_:completionHandler:)
sends a POST request to the Mapbox Directions API instead of sending a GET request that returns an error. (#341) - When possible,
Directions.calculateRoutes(matching:completionHandler:)
now sends a GET request to the Mapbox Map Matching API instead of a POST request. (#341) - Fixed an issue where certain waypoint names would cause
Directions.calculateRoutes(matching:completionHandler:)
to return an error. (#341) - Added the
Directions.url(forCalculating:httpMethod:)
andDirections.urlRequest(forCalculating:)
methods for implementing custom GET- and POST-compatible request code. (#341) - Added the
Waypoint.separatesLegs
property, which you can set tofalse
to create a route that travels “via” the waypoint but doesn’t stop there. Deprecated theMatchOptions.waypointIndices
property in favor ofWaypoint.separatesLegs
, which also works withRouteOptions
. (#340) - Fixed unset properties in
Waypoint
objects that are included in a calculatedRoute
s orMatch
es. (#340) - Added
DirectionsResult.fetchStartDate
andDirectionsResult.requestEndDate
properties. (#335) - Added a
DirectionsOptions.urlQueryItems
property so that subclasses ofRouteOptions
andMatchOptions
can add any additional URL query parameters that are supported by the Mapbox Directions and Map Matching APIs. (#343)
Documentation is available online or within Xcode.
v0.26.1
Waypoint
s andTracepoint
s can now be compared for object equality. (#331)- Fixed an issue where the
DirectionsResult.accessToken
andDirectionsResult.apiEndpoint
properties failed to roundtrip throughNSCoder
. (#331) Route
now supports secure coding via theNSSecureCoding
protocol. (#331)- Fixed an issue where
Intersection
failed to decode when an outlet road has no road classes (i.e., a normal road that isn’t a bridge, tunnel, toll road, or motorway). (#331)
Documentation is available online or within Xcode.
v0.26.0
- Renamed
CoordinateBounds(_:)
toCoordinateBounds(coordinates:)
. (#325) - Added a
Waypoint.targetCoordinate
property for specifying a more specific destination for arrival instructions. (#326) - Fixed an issue where the
Waypoint.allowsArrivingOnOppositeSide
property was not copied when copying aWaypoint
object. (#326)
Documentation is available online or within Xcode.
v0.25.2
v0.25.1
- Added the
Directions.apiEndpoint
andDirections.accessToken
properties that reflect the values passed into theDirections
class’s initializers. (#313) - Fixed an issue causing some requests with many waypoints or long waypoint names to fail. (#311)
- Fixed an issue where some requests with very many waypoints would fail silently. (#314)
Documentation is available online or within Xcode.
v0.25.0
v0.24.1
v0.24.0
v0.23.0
v0.22.0
- Added the
VisualInstructionBanner.tertiaryInstruction
property for additional information to display, such as a lane configuration or subsequent turn. Renamed theVisualInstruction.textComponents
property toVisualInstruction.components
. Some of the components may beLaneIndicationComponent
objects, representing a lane at an intersection. #258 - Fixed a bug which caused coordinates to be off by a factor of 10 when requesting
.polyline6
shape format. #281 - Removed
MBAttributeOpenStreetMapNodeIdentifier
, as it is no longer being tracked by the API. This is a breaking change. #275
Documentation is available online or within Xcode.