#587 feat(frontend): add offline/network error handling with graceful…#605
#587 feat(frontend): add offline/network error handling with graceful…#605Feyisara2108 wants to merge 3 commits intoLabsCrypt:mainfrom
Conversation
… graceful degradation and auto-retry # Conflicts: # frontend/src/app/layout.tsx
d2f429d to
28035a9
Compare
ogazboiz
left a comment
There was a problem hiding this comment.
Frontend Prettier check is failing. Run this from the frontend/ directory and commit:
cd frontend
npx prettier --write .
git add -A
git commit -m 'style: apply prettier formatting'
git pushAlso rebase on main afterward to pick up a recent test fix in eventIndexer.test.ts.
|
The codebase issues on main have been resolved and all CI checks are passing now. Please rebase your branch to pull in the latest changes before continuing. Thanks for your patience. |
ogazboiz
left a comment
There was a problem hiding this comment.
Has merge conflicts. The retry callback returns true unconditionally when offline, which means infinite retries. Cap retries even for network errors. The eventIndexer test changes are unrelated to the offline feature. staleTime jump from 60s to 5 minutes is aggressive for financial data.
|
heads up, a few important changes just landed on main that affect your PR:
please rebase on latest main: git fetch upstream
git rebase upstream/main
git push --force-with-lease |
#587 feat(frontend): add offline/network error handling with graceful degradation and auto-retry
Summary
Implements resilient offline support by adding a network status banner, React Query caching fallbacks, auto-retry on reconnect, and a global error boundary—ensuring users always see meaningful UI even when the backend is unreachable.
Changes
staleTime,gcTime, and smart retry logic for network errorsOfflineBannercomponent: shows "You're offline" banner usingnavigator.onLineNetworkErrorBoundaryfor graceful fallback UI on unhandled fetch failuresonlineeventUser Experience
Technical Details
anytypesTesting
Issue
Closes #587