Skip to content

fix(frontend): re-throw login and signup API exceptions from AuthContext (fix #96)#124

Merged
nirakarpatel merged 1 commit into
niharika-mente:mainfrom
Pratyush-Panda-2006:fix-swallowed-auth-exceptions-issue-96
Jul 8, 2026
Merged

fix(frontend): re-throw login and signup API exceptions from AuthContext (fix #96)#124
nirakarpatel merged 1 commit into
niharika-mente:mainfrom
Pratyush-Panda-2006:fix-swallowed-auth-exceptions-issue-96

Conversation

@Pratyush-Panda-2006

Copy link
Copy Markdown
Contributor

Description

This pull request fixes a bug where the Login and Signup pages always display generic failure messages instead of context-specific error feedback (like "Account not found", "User already exists", or "Server error").

The login and register functions in AuthContext.jsx were catching Axios API exceptions, printing them, and returning false. This swallowed the exception and prevented the try...catch block inside Login.jsx and Signup.jsx from catching specific status codes.

Changes

  • Updated frontend/src/context/AuthContext.jsx to re-throw exceptions (throw error) in the catch blocks of both login and register handlers.

Fixes #96

@coderabbitai

coderabbitai Bot commented Jul 8, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@Pratyush-Panda-2006, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 42 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: c09c7d5e-4309-4acc-8b05-3daeeb82447e

📥 Commits

Reviewing files that changed from the base of the PR and between 87148ba and 2a791a8.

📒 Files selected for processing (1)
  • frontend/src/context/AuthContext.jsx
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@nirakarpatel nirakarpatel added bug Something isn't working SSoC26 Medium labels Jul 8, 2026
@nirakarpatel nirakarpatel merged commit 8f99509 into niharika-mente:main Jul 8, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working Medium SSoC26

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] Login and Signup pages always show generic error due to swallowed exceptions in AuthContext

2 participants