- Notifications
You must be signed in to change notification settings - Fork320
0.23.0 Migration Guide
Pablo Guardiola edited this pageDec 21, 2018 ·2 revisions
- Remove MapboxNavigationOptions ignored by Navigator
- Remove LocationValidator and force last Location if found
- Add RouteProgressState to RouteProgress for current Navigator information
- Allow access to AlertView and the ability to enable or disable
InRemove MapboxNavigationOptions ignored by Navigator the followingMapboxNavigationOptions were removed:
maxTurnCompletionOffset();maneuverZoneRadius();maximumDistanceOffRoute();deadReckoningTimeInterval();maxManipulatedCourseAngle();userLocationSnapDistance();secondsBeforeReroute();snapToRoute();enableOffRouteDetection();manuallyEndNavigationUponCompletion();metersRemainingTillArrival();minimumDistanceBeforeRerouting();
These options were removed, because with the introduction ofNavigator inhttps://github.com/mapbox/mapbox-navigation-android/pull/1265, we are no longer considering them in our core processing logic. We are going to look into allowing more configuration again as time progresses.
InRemove LocationValidator and force last Location if found, we remove theMapboxNavigationOption#locationAcceptableAccuracyInMetersThreshold(). We did this because this option was also not being considered.Navigator has its ownLocation filtering algorithms that will reject / accept updates for processing.
Add RouteProgressState to RouteProgress for current Navigator information we broke ourRouteUtils API. Detecting an arrival event withRouteUtils#isArrivalEvent now only requires aRouteProgress:
// OLDrouteUtils.isArrivalEvent(@NonNull RouteProgress routeProgress, @NonNull Milestone milestone)// NEW@Overridepublic void onProgressChange(Location location, RouteProgress routeProgress) { RouteUtils routeUtils = new RouteUtils(); boolean isArrival = routeUtils.isArrivalEvent(routeProgress);}