mapbox / mapbox/mapbox-navigation-android
Introduce geometry cache protection
Open
Nobody has claimed this yet.
feature
jira-sync-complete
op-ex
- Dominant language
- Kotlin
- Stars
- 651
- Forks
- 321
- PR merge metrics
- No merged PRs in 30d
Description
As a follow-up to #4720 we should consider introducing a protected cache feature, so that we can be confident that the routes the SDK internally depends on cannot be evicted from the cache by developers who use the `DecodeUtils` for other purposes.
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 follow-up issue #4720 and the DecodeUtils entry point to understand the existing cache behavior and which routes the SDK depends on. Define how protected entries should behave when developers use DecodeUtils for other purposes, then verify that internal routes cannot be evicted.
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
- 35/100