Łukasz Paczos
Łukasz Paczos
Thanks @abhishek1508, I somehow missed that comment focusing on the data side of things. Let's copy the arguments here and continue! From @cafesilencio: I disagree. These are completely different things....
From my side I'd like to add that these features certainly are related and that's enforced by the Navigation APIs - they all come as URIs under a guidance view...
The migration is going to be much easier when Nav Native's `RouterInterface` returns a `NavigationRoute`. cc @DenisPryt @SiarheiFedartsou
Refs https://github.com/mapbox/mapbox-navigation-native/issues/5554.
cc @MaximAlien for iOS parity
`MapboxServices` are rather stateless, it's only an abstraction to make _a_ request. IMO, if we were to implement a retry logic, SDK should be responsible for driving this experience and...
Hey @takeshi4126, `MapboxNavigation#requestRoutes` is not meant to be used together with the `NavigationView`. `NavigationView` accepts the route as a parameter in the `NavigationViewOptions.Builder#directionsRoute` and you can obtain the route before...
> One issue is that I have to call the MapboxNavigation.requestRoutes() even if I use setRoute() with a DirectionsRoute object obtained separately. Without calling the requireRoutes(), the RouteProgressObserver that I...
Is the proposed behavior that if I create the first instance of route line components and start drawing I don't need to do anything, but if a create a second...
> I"m not exactly sure what you mean by this. The options are for the layers, the colors, the arrow head drawable etc. [...] hat would mean recreating the layers...