Enatega SingleVendor Admin Allowing Gap in Rider Username and Accepting Negative Values in Phone Number Field
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- frontend
Research direction
Start in the rider management section of the Enatega SingleVendor Admin system and reproduce both reported inputs in Chrome: a username containing a space and a negative phone number. Trace the validation for those fields and confirm that both invalid values are rejected; the payload names no files or tests to run.
Written by the indexing model from the issue text.
Description
Describe the bug
I have identified two critical issues in the Enatega SingleVendor Admin system within the rider section. Firstly, the system currently allows users to create rider usernames with gaps, potentially leading to confusion and errors. Secondly, the system accepts negative values in the phone number field, which can impact the ability to contact and manage riders effectively.
To Reproduce
Steps to reproduce the behavior:
Issue 1 (Gap in Rider Username):
Log in to the Enatega SingleVendor Admin system.
Navigate to the rider management section.
Create or edit a rider profile.
Attempt to set a username with a gap (e.g., "john doe" instead of "johndoe").
Issue 2 (Negative Value in Phone Number Field):
Log in to the Enatega SingleVendor Admin system.
Navigate to the rider management section.
Create or edit a rider profile.
Attempt to input a negative value in the phone number field.
Expected behavior
Expected Behavior - Issue 1:
The system should validate and restrict users from creating usernames with gaps, ensuring consistency and preventing potential issues with user identification.
Expected Behavior - Issue 1:
The system should validate and restrict users from creating usernames with gaps, ensuring consistency and preventing potential issues with user identification.
Screenshots
image
Desktop:
Browser : chrome
Additional context
Please investigate and address these issues promptly to enhance the reliability and functionality of the Enatega SingleVendor Admin system.
Thank you for your attention to these matters.
- 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
-
level/task reporter/qa type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
wazuh/wazuh-dashboard-plugins#9310 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
cybersemics/treecrdt#267 ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
wiz-sec-public/backstage-plugin-wiz#16 · 1 comment ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
solana-foundation/solana-com#2245 ·
Maintainers usually reply within 1 day