Retry logic for direction's requests
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 438
- Forks
- 117
- PR merge metrics
- No merged PRs in 30d
Description
Navigation SDK requires retry route requests in case if a response fail with non server-side error(no Internet connection, time out exception, and etc.)
Navigation SDK uses MapboxDirections via MapboxOffboardRouter
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 by reading services-directions/src/main/java/com/mapbox/api/directions/v5/MapboxDirections.java and the referenced MapboxOffboardRouter.kt entry point. Trace how route-request failures are handled, then define and verify retries for non-server-side failures such as unavailable connectivity and timeouts, while leaving server-side failures out of scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, kotlin
- Domain
- api, networking
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100