liquid-labs / liquid-labs/catalyst-core-api
Optimize source invalidation based on involved items.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
My suspicion is that there is some simple analysis we could do to optimize source invalidation based on referenced items. It may be more trouble than it's worth though. This should wait on updating the cache to use URL paths for items.
Depends on #10
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 reviewing the source invalidation and cache implementation, then inspect issue #10 about updating the cache to use URL paths. Determine whether referenced items can safely narrow invalidation after that dependency is complete; done means the optimization is justified and implemented without invalidating unrelated sources.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend, performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100