Implementation of Loading Indicator for Phone Number Verification Page Transition
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 52/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- react, typescript
- Domain
- frontend
Research direction
Start by locating the phone number verification page and the transition triggered after a number is entered, then reproduce the behavior in Chrome. Trace where that transition begins and identify the existing UI state handling; done means a loading indicator is visible while processing and the transition still completes normally.
Written by the indexing model from the issue text.
Description
Describe the bug
Currently, there is a lack of a loading indicator when users enter their phone number for verification on the Multivendor Food Delivery site. This absence of visual feedback may lead to uncertainty about the status of the verification process, causing a potential user experience issue.
To Reproduce
Steps to reproduce the behavior:
Visit the Multivendor Food Delivery site.
Navigate to the phone number verification page.
Enter a phone number for verification.
Observe the absence of a loading indicator during the transition to the next page.
Expected behavior
A loading indicator should be implemented to provide users with visual feedback during the transition to the next page after entering their phone number for verification. This will help users understand that the system is processing their input.
Screenshots
loading.indicator.mp4
Desktop:
Browser: chrome
- 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 patriciaperez90/document-solution-application-react
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
All issues in patriciaperez90/document-solution-application-react
Similar issues
-
engine-rs P3 review-deferral wasm
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
maniator/verticopolis#1154 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
telerik/kendo-react#3861 ·
Maintainers usually reply within 1 day
-
[bug]: use-mobile.ts uses pixel logic, causing UI state de-sync with Tailwind CSS rem breakpointsOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
task
Difficulty 2/5 1-3 hours Newbie friendliness 72/100