fix(validation): Improve name and email error messages for better UX

[Abfa41]

Description

Fixes #6193

This PR improves validation error messages for name and email fields in the resume confirmation schema to provide clearer and more user-friendly feedback.

The previously shared generic error message has been replaced with field-specific messages to avoid confusion during form validation.

Changes made

• Updated name field validation to show:

  • "Name must be at least 2 characters"

• Updated email field validation to show:

  • "A valid email address is required"
  • "Invalid email address"

• Improved consistency and clarity in validation feedback across resume-related schema fields

• Applied changes in the current resumeConfirmDataSchema (as the referenced lines in the issue appear to be outdated)

Benefits

• Clearer validation feedback for users
• Removes misleading shared error messaging
• Improves form usability and debugging experience
• No functional changes to validation logic, only message improvements

Note

The issue references specific lines in lib/validations.ts, but those appear to be outdated in the current codebase. Equivalent validation logic was updated in the active schema implementation.

[vercel]

@Abfa41 is attempting to deploy a commit to the jhasourav07's projects Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

📦 Next.js Bundle Size Report (Gzipped Sizes)

✨ No significant bundle size changes detected.

📊 Summary of Totals

Category	PR Size	Base Size	Difference
Total JS	3697.02 KB	3697.00 KB	+0.01 KB (+0.00%)
Total CSS	296.58 KB	296.58 KB	0 B

[Aamod-Dev]

Splitting the shared 'Name and email are required' generic message into specific messages in lib/validations.ts greatly improves form usability. The 2-character minimum for the name field makes sense too. Approved!

[github-actions]

🎉 Congratulations @Abfa41! Your PR has been successfully merged. 🚀

Thank you for contributing to CommitPulse. Your work helps us build a better tool for the community.

⚠️ Important for GSSoC Contributors:
You are strictly advised to join our Discord Server as it is mandatory for all GSSoC participants. All important announcements, point claims, and community discussions happen there.

Keep building! 💻✨

[Abfa41]

@Aamod-Dev, please check the appropriate label when adding the type labels. We need to add 'type:bug' label instead of 'bug' label, to get the appropriate points in gssoc. Please look into this. Thanks!

[JhaSourav07]

@Aamod-Dev, please check the appropriate label when adding the type labels. We need to add 'type:bug' label instead of 'bug' label, to get the appropriate points in gssoc. Please look into this. Thanks!

type label will be added automatically