hector-jewell / hector-jewell/uber-eats-clone-using-react-native
Typo in "Phone Number Not Verified" message
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
On the Enatega Multivendor app, the message displayed when a phone number is not verified contains a spelling error in the word "Verified".
To Reproduce
Steps to reproduce the behavior:
Go to Profile.
Add a phone number without completing the OTP verification.
Check the message displayed under the phone number field.
Expected behavior
The message should read "Not Verified" with correct spelling.
Desktop (please complete the following information):
OS: [e.g. iOS]
Browser [e.g. chrome, safari]
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 Multivendor Customer App, Bug
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.
Research direction
Start by reproducing the issue in the Profile phone-number flow, then search the codebase for the displayed "Phone Number Not Verified" message. Done means the message reads "Not Verified" with the corrected spelling after an incomplete OTP verification, without changing the surrounding flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react-native
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100