mapbox / mapbox/mapbox-navigation-android
Investigate OffRouteObserver
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 651
- Forks
- 321
- PR merge metrics
- No merged PRs in 30d
Description
Catched from [PR comments ](https://github.com/mapbox/mapbox-navigation-android/pull/3184#discussion_r450312963):
`Asked because we've heard complaints around OffRouteObserver as only pushing back a flag offRoute is not enough and would be great to have more info e.g. in telemetry we need to listen for re-routes via OffRouteObserver AND if true catch right after the first callback from RoutesObserver to update the events accordingly which is kinda complicated and we were wondering if we could push the route chosen back somehow making the API easier to use and consume and provide to clients whole state for when an off-route happens.`
**cc** @mapbox/navigation-android
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 with the linked PR comments and inspect the OffRouteObserver and RoutesObserver APIs mentioned there. Determine what additional off-route state or selected-route information clients need for telemetry and how the callbacks relate. Done means an agreed API direction and documented behavior for off-route and reroute events.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100