Alphabets Accepted in Phone Number Field
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 62/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- mobile
Research direction
Start in the customer app's registration or profile setup flow and locate the phone number input field. Reproduce the issue by entering English letters, then ensure the field rejects non-numeric input or shows validation feedback; verify the expected behavior in both mentioned entry points.
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
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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/full-stack-document-solution
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
All issues in gray-mueller/full-stack-document-solution
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
AOSSIE-Org/DebateAI#611 ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
openzim/mwoffliner#2933 ·
Maintainers usually reply within 1 day
-
Use the README category name for website links and submissionsPossibly taken @dajiaohuang claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
birobirobiro/awesome-shadcn-ui#647 ·
Maintainers usually reply within 2 days
-
Twake Drive picker: closePicker() never destroys the intent (stop() is on the promise returned by start(), not by create())Possibly taken @chibenwa claimed this today. Openclaude
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
linagora/twake-calendar-frontend#1498 · 1 comment ·
Maintainers usually reply within 1 day
-
check:passed streams:add
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day