mapbox / mapbox/mapbox-navigation-android
NavigationView History APIs not available immediately
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 651
- Forks
- 321
- PR merge metrics
- No merged PRs in 30d
Description
Integrating `ReplayLocationEngine` found:
- Currently a client cannot interact with the History APIs when using `NavigationView` until `NavigationView#startNavigation` because `MapboxNavigation` from `NavigationViewModel` (`NavigationView#retrieveMapboxNavigation`) is only created afterwards in `NavigationView#initialize` - a client can enable it right after (that's what I did 😅) but at that point could be late (some events could be missing)
cc @abhishek1508
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing NavigationView#initialize, NavigationView#retrieveMapboxNavigation, and the NavigationViewModel lifecycle around NavigationView#startNavigation, using ReplayLocationEngine as the reported client context. Determine how History APIs can be accessed before navigation starts without missing events; done means clients can interact with them immediately and the relevant events remain available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100