Fix: Restrict email registration to Gmail addresses #174
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.
📌 Linked Issue
🛠 Changes Made
@gmail.comuserController.jsto enforce Gmail-only registration for security@*.comemail🧪 Testing
Ran unit tests (
npm test)Tested manually (describe below):
Test case 1: Entered
test@yahoo.com→ Expected: Error message "Only Gmail addresses are allowed." → Result: Validation blocked successfully.Test case 2: Entered
test@gmail.com→ Expected: Account created successfully → Result: Registration successful.Test case 3: Entered
TEST@GMAIL.COM→ Expected: Registration allowed (case-insensitive check) → Result: Successful.📸 UI Changes (if applicable)
📝 Documentation Updates
✅ Checklist
💡 Additional Notes (If any)
Frontend validation prevents invalid submissions, while backend validation ensures security against API-level bypass attempts.
This ensures consistent and secure enforcement of Gmail-only registration.