Cache Expire
Open
Nobody has claimed this yet.
api
feature request
- Dominant language
- TypeScript
- Stars
- 7.8k
- Forks
- 6.9k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 442
Description
Description
I just recognized that my extension still using old data over months. So I think we should have an option to set a timeout on key. Might be refreshing cache in next session is an idea.
Who will benefit from this feature?
All developers who using Cache API
Anything else?
No response
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 locating the Cache API implementation and reading how keys are currently stored and refreshed. Define the timeout and next-session refresh behavior, then add coverage for expiration; the issue names no files or tests, so repository exploration and design clarification are required.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100