tim-smart / tim-smart/effect-atom
ReactivityKeys: Able to invalidate by namespace
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 792
- Forks
- 49
- PR merge metrics
- No merged PRs in 30d
Description
Say I have a key:
["Users", "GetUser", { id: 1 }]
I would like to be able to invalidate:
["Users", "GetUser", { id: 1 }]User.GetUser with{ id : 1 }query["Users", "GetUser"]all Users.GetUser queries["Users"]all Users queries[]all queries
as an alternative, perhaps invalidate on mutation could be a callback, which may inspect all current keys, and return the subset to invalidate.
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 locating the ReactivityKeys invalidation entry point and the mutation-invalidation path. Compare the requested exact-key and namespace-prefix cases, then clarify whether prefix matching or a callback is the intended design. Add coverage for the listed key scopes and define what invalidating an empty key should do.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100