fix/email-verification-implementation-T126

[Mantra-17]

Team Number : Team 126

Description

This PR implements a comprehensive email verification system that prevents users from auto-logging in after registration. The implementation ensures users must verify their email before accessing protected routes, resolving security concerns and improving user authentication flow.

Related Issue

Closes #109

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• Style/UI improvement

Changes Made

• AuthContext: Removed auto-login logic from registration function

-Registration Flow: Redirects to email verification pending page instead of dashboard

-Login Enhancement: Added 403 error handling for unverified email accounts

-New Page: Created VerifyEmailPending.tsx with clear user instructions

-Route Configuration: Added /verify-email-pending route to App.tsx

-Backend Integration: Proper handling of email verification tokens and status

Testing

• Tested on Desktop (Chrome)
• Tested logic for Start Date and End Date dependencies
• No console errors or warnings
• Code builds successfully

Checklist

• My code follows the project's code style guidelines
• I have performed a self-review of my code
• I have commented my code where necessary
• My changes generate no new warnings
• I have tested my changes thoroughly
• All TypeScript types are properly defined
• Tailwind CSS classes are used appropriately
• Component is responsive across different screen sizes
• I have read and followed the CONTRIBUTING.md guidelines

Additional Notes

This implementation follows security best practices by requiring email verification before granting access. The user flow is designed to be clear and intuitive, with proper error messaging and visual feedback throughout the verification process.

[krishnapaljadeja]

🔍 General Improvement PR — Pending Admin Review

Hey @Mantra-17! Your PR has been received as a General Improvement PR (no linked issue).

Field	Value
Team Number	Team 126
Linked Issue	None

What happens next:

1. An admin will review your changes
2. If approved, an admin will add a level-1 or level-2 label based on complexity
3. Points are calculated automatically when the PR is merged

⚠️ Trivial or low-quality PRs may be closed without merging.
Admin review may take longer than standard PRs.

GDG CHARUSAT Open Source Contri Sprintathon

[krishnapaljadeja]

@Mantra-17 pls fix the description format, add Closes# number also fix the conflicts

[krishnapaljadeja]

✅ PR Validation Passed

Hey @Mantra-17! Your PR looks good. Here is what we found:

Field	Value
Team Number	Team 126
Linked Issue	Closes #109

A maintainer will review your PR within 24–48 hours. Stay responsive to feedback!

GDG CHARUSAT Open Source Contri Sprintathon

[Mantra-17]

Hey I have updated the description pls check it and let me know

[aaleya5]

hey @Mantra-17 please resolve the conflicts. your pr is too farther away from main. take a pull from main before committing.

[Mantra-17]

working on it give me some time

[Mantra-17]

Resolved the issues

[aaleya5]

hey @Mantra-17 your work is still not up to date with main. take a pull from main then merge with your work.

[aaleya5]

hey @Mantra-17 if we dont get any commit in the next hour, we will close this pr.