Alphabets Accepted in Phone Number Field
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 65/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- mobile
Research direction
Locate the phone number input in the Enatega Multivendor Customer App, starting with the registration or profile setup screens described in the issue. Reproduce the alphabet-entry behavior, then verify that non-numeric input is rejected or produces a validation prompt while numeric phone numbers still work.
Written by the indexing model from the issue text.
Description
Description:
While testing the Enatega Multivendor Customer App, I observed a critical issue where the phone number input field allows the entry of English alphabets. This poses a significant problem as phone numbers typically consist of numerical digits only, and accepting alphabets may lead to user errors and hinder the user experience.
Steps to Reproduce:
Open the Enatega Multivendor Customer App.
Navigate to the section where the phone number is entered (e.g., during registration or profile setup).
Attempt to enter English alphabets instead of numerical digits in the phone number field.
Expected Behavior:
The phone number input field should only allow the entry of numerical digits. An error message or validation prompt should be displayed if alphabets are entered.
Actual Behavior:
The phone number input field accepts English alphabets without providing any error or validation prompt.
image
Activity
- 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/ride-sharing-solution-application
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
All issues in gray-mueller/ride-sharing-solution-application
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