[Bug]: Sign-up form accepts invalid names containing numbers and special characters

[sujitha-kotyada]

Bug Description

The sign-up form currently allows users to enter invalid values in the Full Name field, including numbers and special characters (e.g., 12345, @@@, John123).

Since the full name is used for user profile information and may be split into first and last names internally, accepting invalid input can lead to inconsistent user data and unexpected behavior.

The application should validate the Full Name field and only allow alphabetic characters and spaces.

Steps to Reproduce

1. Open the Sign Up page.
2. Enter an invalid value in the Full Name field (e.g., 12345 or John@123).
3. Fill in the remaining required fields with valid data.
4. Submit the registration form.
5. Observe that the registration proceeds without validating the Full Name field.

Expected Behavior

The Full Name field should:

• Accept only alphabetic characters and spaces.
• Reject names containing numbers or unsupported special characters.
• Display a clear validation message before form submission.

Actual Behavior

The application accepts invalid names containing numbers or special characters and allows the registration request to proceed without validation.

Severity

Medium

Screenshots / Screen Recording

N/A

Browser

Google Chrome

Operating System

Windows 11

Additional Context

Adding client-side validation for the Full Name field will improve data quality and provide immediate feedback to users before form submission.

A simple regular expression (or equivalent validation logic) can be used to ensure that only alphabetic characters and spaces are accepted.

[sujitha-kotyada]

/assign

Hi @Canopus-Labs @KaranUnique ,
Please assign this issue to me under GSSoC'2026,
Thank you.

[guruprasad06]

Hi @Canopus-Labs @KaranUnique ,

I've submitted PR #404 for this issue. Looking forward to your review.

Thank you!