Navigation Back Functionality Issue during Email Verification on Enatega Multivendor Customer Website.
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- javascript, react-native
- Domain
- authentication, frontend
Research direction
No files, tests, or entry points are identified. Reproduce the email-verification flow in the customer website, trace the back-navigation behavior, and verify that the previous verification step is reachable without disrupting the flow.
Written by the indexing model from the issue text.
Description
Issue: Navigation Back Functionality Issue during Email Verification on Enatega Multivendor Customer Website
Description:
There is a navigation issue on the Enatega Multivendor Customer Website during the email verification process. The "navigation back" function does not work properly, impacting the user's ability to return to the previous page or step.
Impact:
User Experience: The malfunctioning navigation back feature can frustrate users and affect their overall experience on the website.
Process Flow: The issue disrupts the expected flow of the email verification process, potentially causing confusion.
Steps to Reproduce:
Access the Enatega Multivendor Customer Website.
Proceed to the email verification process.
Attempt to use the "navigation back" function to return to the previous step.
Observe that the function does not work as expected.
Expected Resolution:
The navigation back functionality during email verification should be addressed and fixed to ensure that users can navigate smoothly and return to the previous step when needed. This will enhance the user experience and maintain a logical process flow.
Capture Screenshot 2023-10-23 112254 Ca
- Dominant language
- JavaScript
- 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 raymondjames090/uber-eats-app-clone-using-react-native
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
raymondjames090/uber-eats-app-clone-using-react-native#2069 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
raymondjames090/uber-eats-app-clone-using-react-native#2003 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
raymondjames090/uber-eats-app-clone-using-react-native#2002 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
raymondjames090/uber-eats-app-clone-using-react-native#1979 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
raymondjames090/uber-eats-app-clone-using-react-native#1978 ·
All issues in raymondjames090/uber-eats-app-clone-using-react-native
Similar issues
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100