Releases: mapbox/mapbox-java
Releases · mapbox/mapbox-java
Mapbox Java SDK v6.0.0
No additional changes. No issues were identified during testing and the last pre-release has been promoted to stable.
The full list of changes for v6.0.0 is available here.
Mapbox Java SDK v6.0.0-alpha.9
Fixed RouteOptions#toUrl()
function. #1302
Mapbox Java SDK v6.0.0-alpha.8
- Exposed
RouteOptions#toUrl()
function.
Mapbox Java SDK v6.0.0-alpha.7
- Exposed include-hov/hot parameters and added exclude list option #1296
Mapbox Java SDK v6.0.0-alpha.6
- Added support for
active_direction
encapsulated in lane banner component. #1294
Mapbox Java SDK v6.0.0-alpha.5
Mapbox Java SDK v6.0.0-alpha.4
Mapbox Java SDK v6.0.0-alpha.3
- Bumped
okhttp
version to4.9.0
. It requires java 1.8 for compatibility. #1271
Mapbox Java SDK v6.0.0-alpha.2
- Removed
accessToken
fromRouteOptions
and moved it toMapboxDirections
instead. This simplifies serialization and deserialization of route objects without potential leaks of data under the assumption that an entity that makes a route request has an ability to provide an access token without the route object having to transport it. #1276
Mapbox Java SDK v6.0.0-alpha.1
- Refactored
MapboxDirections
to acceptRouteOptions
as an argument that defines request parameters #1265 ⚠️ Added a List overload inRouteOptions
for coordinates, now there areRouteOptions#coordinates(string)
andRouteOptions#coordinatesList(list)
. If there are routes that were previously serialized withtoJson
methods and containedRouteOptions
, 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 serializedrouteOptions
, change thecoordinates
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 hasrouteOptions
property, you need to explicitly provide an access token inDirectionsRoute#fromJson(routeJson, accessToken)
or an exception will be thrown. #1267- Moved the
requestUuid
object out ofRouteOptions
and intoDirectionsRoute
since the UUID is not a request parameter, it's a response value #1265 - Added
enableRefresh
toRouteOptions
since it is a route request parameter #1265 - Removed a separate
WalkingOptions
in favor of storing the parameter directly in theRouteOptions
#1265 - Exposed
arriveBy
anddepartAt
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