Skip to content

fix(backend): check if user exists on registration to prevent raw database errors (fix #94)#122

Merged
nirakarpatel merged 2 commits into
niharika-mente:mainfrom
Pratyush-Panda-2006:fix-duplicate-signup-issue-94
Jul 8, 2026
Merged

fix(backend): check if user exists on registration to prevent raw database errors (fix #94)#122
nirakarpatel merged 2 commits into
niharika-mente:mainfrom
Pratyush-Panda-2006:fix-duplicate-signup-issue-94

Conversation

@Pratyush-Panda-2006

Copy link
Copy Markdown
Contributor

Description

This pull request prevents raw database validation errors and key constraints leakages when registering a duplicate email account. Previously, the endpoint did not check if the email address was already taken, letting Mongoose throw a raw MongoDB duplicate key constraint violation error (11000) that propagated to the client.

Changes

  • Updated backend/src/controllers/userAuth.js to execute await User.findOne({ email }) before creation.
  • Returns a clean 400 Bad Request status code with a user-friendly error message if a duplicate user is found.

Fixes #94

@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: 34 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: 944c574d-ae2a-4740-90a5-51300a45cf55

📥 Commits

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

📒 Files selected for processing (2)
  • backend/src/Utils/Validetor.js
  • backend/src/controllers/userAuth.js
✨ 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.

Comment thread backend/src/controllers/userAuth.js Fixed
@nirakarpatel nirakarpatel added bug Something isn't working SSoC26 Hard labels Jul 8, 2026
@nirakarpatel nirakarpatel merged commit 7d0c851 into niharika-mente:main Jul 8, 2026
3 of 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 Hard SSoC26

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG/SECURITY] Duplicate registration attempts expose raw database errors

3 participants