Full Name Field Accepts Numbers on Sign-Up Page – Enatega Multivendor
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- react, typescript
- Domain
- authentication, frontend
Research direction
Start at the Enatega Multivendor sign-up page and reproduce the issue with a value such as John123 in the Full Name field. Locate the field's validation and submission behavior, then verify that numbers are rejected with an error and invalid user data is not saved.
Written by the indexing model from the issue text.
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
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
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.
More from gray-mueller/restaurant-ordering-system-using-react-js
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
gray-mueller/restaurant-ordering-system-using-react-js#611 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
gray-mueller/restaurant-ordering-system-using-react-js#609 ·
-
Difficulty 2/5 1-2 days Newbie friendliness 68/100
gray-mueller/restaurant-ordering-system-using-react-js#598 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
gray-mueller/restaurant-ordering-system-using-react-js#592 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
gray-mueller/restaurant-ordering-system-using-react-js#591 ·
All issues in gray-mueller/restaurant-ordering-system-using-react-js
Similar issues
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100