Language Change Requires App Refresh on Enatega Multivendor Food Delivery Website
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- javascript, react-native
- Domain
- frontend, internationalization
Research direction
Start by reproducing the language change from the user profile or settings as both a logged-in user and a guest, then trace the React Native localization flow responsible for applying the preference. Done means the selected language appears immediately throughout the app without a manual refresh.
Written by the indexing model from the issue text.
Description
Issue Description:
Summary:
Users are currently experiencing an inconvenience on the Enatega Multivendor Food Delivery website, where changing the language requires a manual refresh of the entire application. This disrupts the user experience and can lead to frustration.
Steps to Reproduce:
Navigate to the Enatega Multivendor Food Delivery website.
Login to your account or proceed as a guest.
Locate the language settings option in the user profile or settings.
Change the language preference to a different option.
Observe that the language does not update immediately, and a manual refresh of the entire app is required.
Expected Behaviour:
Changing the language preference should reflect instantaneously without the need for a manual refresh. Users should be able to seamlessly experience the website in their preferred language.
Actual Behavior:
The language change is not applied until the user manually refreshes the entire app, causing an interruption in the user experience.
04.12.2023_14.26.19_REC.mp4
- 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