-
Notifications
You must be signed in to change notification settings - Fork 0
Fix promise-swr revalidation #12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR fixes a bug in the promise-swr library where multiple concurrent calls could trigger multiple revalidations during the stale-while-revalidate process. The fix adds a check to prevent revalidation when one is already in progress.
- Adds a condition to prevent concurrent revalidations by checking
!cached.revalidating - Removes the debug dependency and all debug logging statements
- Improves TypeScript documentation with generic type parameters
Reviewed Changes
Copilot reviewed 3 out of 5 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| packages/promise-swr/src/index.js | Fixes concurrent revalidation bug, removes debug logging, and adds TypeScript-style documentation |
| packages/promise-swr/package.json | Removes debug dependency and bumps version to 1.0.2 |
| packages/promise-swr/README.md | Adds documentation clarifications for maxAge and resolver options |
fee1385 to
3ccc412
Compare
3ccc412 to
ca7dd1e
Compare
This PR fixes a minor bug when revalidating in
promise-swr: If multiple calls to the wrapper were executed, multiple calls to the wrapped functionfncould be made during the time it would take to revalidate (34be133).Several other documentation and minor improvements were added.
PS: Thanks Copilot for helping me find this improvement opportunity!
Process checklist
Metrics
Actual effort: 1.5h