Full Name Field Accepts Numbers on Sign-Up Page – Enatega Multivendor

Open Beginner friendly
#2,487 0 comments 0 reactions 0 assignees View on GitHub

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
javascript
Domain
authentication, frontend

Research direction

Start at the Enatega Multivendor sign-up page and trace the Full Name field's validation and submission flow. Reproduce the John123 case, then verify that invalid characters are rejected with an error and valid names containing permitted separators still submit successfully.

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
JavaScript
Stars
3
Forks
5
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from lambertf917/react-native-uber-eats-clone

All issues in lambertf917/react-native-uber-eats-clone

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.