Option to force single file for both metadata and contents (no side loading for content)
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 166
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
Right now two files are stored for each cache entry: one for metadata and the other for the contents. This is typically for performance reasons (you don’t want to read the entire cache file contents to check the cache key).
It might be useful to have an option to disable this feature when the metadata and content are being stored outside of the .cache folder, thinking about https://www.zachleat.com/web/transcripts/ (putting transcripts in the repo)
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
No file, test, or entry point is named. Start by locating the cache storage code and tracing how metadata and contents are written and read; done means an option stores both in one file while retaining the existing two-file behavior by default.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100