fix(frontend): re-throw login and signup API exceptions from AuthContext (fix #96)#124
Conversation
|
Warning Review limit reached
Next review available in: 42 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Description
This pull request fixes a bug where the
LoginandSignuppages always display generic failure messages instead of context-specific error feedback (like "Account not found", "User already exists", or "Server error").The
loginandregisterfunctions inAuthContext.jsxwere catching Axios API exceptions, printing them, and returningfalse. This swallowed the exception and prevented thetry...catchblock insideLogin.jsxandSignup.jsxfrom catching specific status codes.Changes
frontend/src/context/AuthContext.jsxto re-throw exceptions (throw error) in the catch blocks of bothloginandregisterhandlers.Fixes #96