options.buffer seems never judge whether the file is fresh
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 291
- Forks
- 48
- PR merge metrics
- No merged PRs in 30d
Description
use buffer means never have the new file ?
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
No file or test is named; start by locating the options.buffer handling in the static-cache middleware and its existing tests. Clarify how freshness and newly created files should behave, then verify the expected behavior with a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100