Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🐞Bug: Register page name field validation is missing #548

Closed
AVNI-THEEXPLORER opened this issue Jan 3, 2025 · 7 comments · Fixed by #549
Closed

🐞Bug: Register page name field validation is missing #548

AVNI-THEEXPLORER opened this issue Jan 3, 2025 · 7 comments · Fixed by #549
Assignees

Comments

@AVNI-THEEXPLORER
Copy link
Contributor

Description

On the Register page, the name field validation is missing. Currently, the name field accepts numbers and letters.It can create a problem in the backend database.

Steps to Reproduce:

Navigate to the Register page.
In the "Name" field, input invalid data such as:

  1. Numbers (e.g., 12345)
  2. Special characters (e.g., @#$%^&*)
  3. Extremely long strings (e.g., 500+ characters)

Attempt to submit the form.
Observe that the form accepts invalid inputs without any errors or warnings.

Screenshot

image

Expected Behaviour:

The "Name" field should have proper validation to ensure:

  1. Only alphabetic characters (and optionally spaces or hyphens) are allowed.
  2. Input length is reasonable (e.g., between 2 and 50 characters).
  3. Special characters and numeric inputs are restricted.

Actual Behavior:

The "Name" field lacks validation, allowing any input to be submitted without restrictions.

Impact:

  1. May result in improper user data stored in the database.
  2. Could lead to errors in other parts of the application that depend on clean user data.
  3. Reduces user experience and professionalism of the registration process.

Proposed Solution:

Implement front-end validation using HTML5 attributes like pattern or JavaScript.

Environment:

  1. Browser: Chrome
  2. OS: Windows 11
  3. Priority: High
Copy link
Contributor

github-actions bot commented Jan 3, 2025

Thank you for raising this issue! We'll look into it as soon as possible. Please ensure that the issue is not duplicate, and you read CONTRIBUTING.md carefully. Your contributions are highly appreciated! 😊

@AVNI-THEEXPLORER
Copy link
Contributor Author

@dhairyagothi please assign me with this issue

@firdoush01
Copy link

@dhairyagothi kindly assign me this work under SWOC

@AVNI-THEEXPLORER
Copy link
Contributor Author

@firdoush01 i have been pre assigned both issues and i will be merging my pr today for both issues you could find some new issues for yourself

@AkanshaOP
Copy link

please assign me this

@AVNI-THEEXPLORER
Copy link
Contributor Author

@AkanshaOP i have been pre assigned both issues and i will be merging my pr today for both issues you could find some new issues for yourself

Copy link
Contributor

Hello @AVNI-THEEXPLORER! Your issue #548 has been closed. Thank you for your contribution!

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

Successfully merging a pull request may close this issue.

4 participants