Skip to content

cleanup(backend): rename Validetor utility to Validator and utilize validator library (fix #127)#131

Open
Pratyush-Panda-2006 wants to merge 1 commit into
niharika-mente:mainfrom
Pratyush-Panda-2006:cleanup-validator-utility-issue-127
Open

cleanup(backend): rename Validetor utility to Validator and utilize validator library (fix #127)#131
Pratyush-Panda-2006 wants to merge 1 commit into
niharika-mente:mainfrom
Pratyush-Panda-2006:cleanup-validator-utility-issue-127

Conversation

@Pratyush-Panda-2006

Copy link
Copy Markdown
Contributor

Description

This pull request cleans up the backend validation logic. It fixes a spelling typo in the validator helper file name (renaming Validetor.js to Validator.js) and updates its import path in userAuth.js. Furthermore, it replaces custom email and password length regular expression checks with standard methods from the imported validator package.

Changes

  • Renamed backend/src/Utils/Validetor.js to backend/src/Utils/Validator.js and updated imports in backend/src/controllers/userAuth.js.
  • Refactored validation functions to use validator.isEmail and validator.isLength alongside strict type validations.

Fixes #127

@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: 24 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: 82562c60-1fbc-4d59-b85c-e495085e8f15

📥 Commits

Reviewing files that changed from the base of the PR and between a3fcb95 and 11337e2.

📒 Files selected for processing (3)
  • backend/src/Utils/Validator.js
  • 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[CLEANUP] Unused validator import and file name typo in Validetor utility

1 participant