Cache and "refresh" behavior not clear
Open
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 287
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
If the `cacheExpirationMs` is 1 minute and `minWaitTimeBetweenSyncMs` is 5 minutes, what will happen when I do a `getCurrentTime()` at minute 3? Will the value in the cache be used even though it is expired, will a sync be forced even though it still has 2 minutes left or will it just use the local device time?
Contributor guide
No contributing guide indexed for this repository
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 the cacheExpirationMs and minWaitTimeBetweenSyncMs handling around getCurrentTime(). Verify the minute-3 scenario, then document the resulting behavior and update the relevant documentation or usage guidance; the issue does not name a file or test to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100