Language Inconsistency in Cart Message After Switching Language to Arabic
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
- localization, mobile
Research direction
Reproduce the issue in the Enatega Multivendor Customer App by switching to Arabic, adding cart items, selecting another restaurant, and adding another item on both iPhone and Android. Trace the cart and restaurant-selection message to its localization source. Done means the message appears in Arabic consistently after the language switch and the behavior is verified across the reported devices.
Written by the indexing model from the issue text.
Description
Describe the bug
Users of the Enatega Multivendor Customer App encounter a language inconsistency issue when switching the app language to Arabic. If there are already items in the cart, and the user selects a different restaurant, adding an item to the cart displays a message that remains in English instead of switching to Arabic.
To Reproduce
Steps to reproduce the behavior:
Open the Enatega Multivendor Customer App.
Log in with valid credentials.
Switch the app language to Arabic.
Add items to the cart.
Select a different restaurant and add an item to the cart.
Observe the language inconsistency in the message displayed.
Expected behavior
When switching the app language to Arabic, all user-facing messages, including those related to the cart and restaurant selection, should be displayed in Arabic for a consistent user experience.
Screenshots
WhatsApp Image 2024-01-10 at 19 35 38_cb52bd9a
Smartphone:
Device: iPhone and android
Additional context
This issue has been reported by users consistently.
The problem persists across different devices.
- 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