lambertf917 / lambertf917/laundry-solution-app-react
Full Name Field Accepts Numbers on Sign-Up Page – Enatega Multivendor
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
On the Enatega Multivendor website’s sign-up page, the “Full Name” field allows numbers to be entered along with the name, and the form still saves successfully. This can lead to invalid or inaccurate user information being stored.
To Reproduce
Steps to reproduce the behavior:
Go to the Enatega Multivendor website sign-up page.
In the “Full Name” field, enter a name containing numbers (e.g., John123).
Complete the rest of the required fields and submit the form.
See that the form saves the data without any error.
Expected behavior
The “Full Name” field should only allow alphabetic characters (with spaces, hyphens, or apostrophes if needed) and should not accept numbers. An error message should be displayed if the user enters invalid characters.
Desktop (please complete the following information):
OS: [e.g. Desktop]
Browser [e.g. chrome]
Version [e.g. 22]
Smartphone (please complete the following information):
Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]
Additional context
Add any other context about the problem here.
Labels: Enatega Website, Bug
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the sign-up page and trace the Full Name field to its client-side validation and form submission handling. Reproduce the John123 case, then verify that numeric characters are rejected and an error is shown without saving the form.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authentication, frontend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100