mapbox / mapbox/mapbox-navigation-android
Add ability to specify which route is considered primary
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 651
- Forks
- 321
- PR merge metrics
- No merged PRs in 30d
Description
Currently the route at index 0, if exists, will be treated as the primary route for Active Guidance. Maybe we should introduce an explicit `route index` instead of using the route at index 0 as the primary route, so that the user won't have to reorder them. But that would require some refactoring, see https://github.com/mapbox/mapbox-navigation-android/pull/4739#issuecomment-909125619.
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 reviewing how Active Guidance selects the route at index 0 and read the refactoring discussion in pull request 4739. The work is done when callers can explicitly designate the primary route without reordering the route collection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100