Skip to content

Mapbox Java SDK v6.0.0-alpha.1

Pre-release
Pre-release
Compare
Choose a tag to compare
@korshaknn korshaknn released this 20 Jul 14:11
· 184 commits to main since this release
692c855
  • Refactored MapboxDirections to accept RouteOptions as an argument that defines request parameters #1265
  • ⚠️ Added a List overload in RouteOptions for coordinates, now there are RouteOptions#coordinates(string) and RouteOptions#coordinatesList(list). If there are routes that were previously serialized with toJson methods and contained RouteOptions, they will not be possible to deserialize anymore since coordinates are now stored as a string and not an array. This breaking change can typically impact test fixtures. To address the change in your existing serialized routeOptions, change the coordinates array to a semicolon-separated string, for example:
- "coordinates":[[-122.5237429,37.975393],[-122.5231413,37.9750695]]
+ "coordinates":"-122.5237429,37.975393;-122.5231413,37.9750695"
  • ⚠️ Stopped serializing access tokens. This means that if you're deserializing a route that has routeOptions property, you need to explicitly provide an access token in DirectionsRoute#fromJson(routeJson, accessToken) or an exception will be thrown. #1267
  • Moved the requestUuid object out of RouteOptions and into DirectionsRoute since the UUID is not a request parameter, it's a response value #1265
  • Added enableRefresh to RouteOptions since it is a route request parameter #1265
  • Removed a separate WalkingOptions in favor of storing the parameter directly in the RouteOptions #1265
  • Exposed arriveBy and departAt request parameters #1265
  • Exposed ANNOTATION_CONGESTION_NUMERIC parameter #1265
  • Updated documentation for various route request parameters #1265
  • Exposed DirectionsResponse#fromJson(json, route options, request uuid) that allows to provide information about the original route request which response they deserialize so that Nav SDK can operate correctly #1265
  • Exposed DirectionsRoute#fromJson(json, route options, request uuid) for same reason as above #1265
  • Exposed RouteOptions#fromUrl utility function that creates the object from the request URL which might be useful when paired with the above functions #1265
  • Added default values for RouteOptions: base URL, user, and geometry encoding (polyline6) #1265
    #1265
  • Fixed an issue where coordinates were rounded to 6 decimal places instead of 7 decimal places that the GeoJSON specification expects #1265
  • Changed the default encoding for MapMatching to be polyline6 and aligns it with regular route requests #1265
  • Added a Bearing object that represents a pair of values for {angle, degrees} #1265
  • Removed route request parameters verification in favor of letting the service respond with a correct error #1265
  • Replaced Closure @Nullable annotations with @NonNull #1268