feat/157-frontend-route-guards-auth-checks - #219
Open
Wetshakat wants to merge 2 commits into
Open
Conversation
|
@Wetshakat is attempting to deploy a commit to the Jaja's projects Team on Vercel. A member of the Team first needs to authorize it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
closed #157
PR Title
Frontend: Add Centralized Toasts and Protected Auth Routes
Summary
This PR introduces a centralized toast notification system for consistent frontend feedback and adds authentication-based route protection for wallet-dependent pages.
Changes
Added a global toast context/provider.
Added a reusable toast component with dismiss actions and stacked notifications.
Added styling and animations for success, error, warning, and info notifications.
Wrapped the application with the toast provider.
Replaced inline task submission errors with centralized toast notifications.
Added dashboard error toasts for failed data fetches.
Added toast notifications for failed recent-task requests.
Added API-layer notifications for:
503retry warnings.401wallet disconnect/session expiry.Added protected route guards for authenticated pages.
Why
The frontend previously used inconsistent error-handling patterns, including inline error messages, silent console errors, and limited feedback during retry or wallet-session failures.
This update provides a consistent notification UX and ensures protected routes fail closed, preventing unauthenticated users from rendering wallet-dependent content.
Validation
Notes
The production build reports a non-blocking Vite bundle-size warning. The build itself completes successfully and the implemented features are working as expected.