fix: persist unread notification count across refreshes#1116
Conversation
|
@seffhunnn is attempting to deploy a commit to the PRIYANSHU DOSHI's projects Team on Vercel. A member of the Team first needs to authorize it. |
GSSoC Label Checklist 🏷️@Priyanshu-byte-coder — please apply the appropriate labels before merging: Difficulty (pick one):
Quality (optional):
Validation (required to score):
|
|
Playwright smoke tests are failing on this PR. Check the CI logs, fix failing tests, then push an update. Cannot merge while tests are red. |
|
Playwright smoke tests are failing on this PR. Please check the E2E test failures and fix them before merging. |
|
hii @Priyanshu-byte-coder i synced the latest playwright workflow fixes into this branch, verified that the ci issue was caused by the previous playwright version mismatch, and confirmed that e2e tests, lint, and type checks are now all passing successfully. |
84f0116
into
Priyanshu-byte-coder:main
|
🎉 Merged! Thanks for contributing to DevTrack. If the project has been useful to you, a ⭐ star on the repo is the easiest way to support it — it helps DevTrack get discovered by more developers. Keep an eye on open issues for your next contribution! |
Summary
Fixed the unread notification badge flicker after page refresh by persisting the last known unread count in localStorage and restoring it immediately on initial render before the client-side fetch completes.
Closes #1031
Type of Change
Changes Made
How to Test
Steps for the reviewer to verify this works:
npm run devCtrl + R0Slow 3Gdevtrack:unread-notification-countis stored correctly0without crashingnpm run lintnpm run type-checkScreenshots (if UI change)
N/A
Checklist
npm run lintpasses locallynpm run type-check)