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
- typescript
- Domain
- internationalization, mobile-dev
Research direction
Start by reproducing the cart flow on iPhone or Android with the app language set to Arabic: add items, switch restaurants, and add another item. Trace the user-facing message triggered by that action and identify where its language is selected. Done means the message appears in Arabic after the language switch and remains consistent across both reported device types.
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
- 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 gray-mueller/full-stack-document-solution
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
All issues in gray-mueller/full-stack-document-solution
Similar issues
-
enhancement providers-api ui-dashboard
Difficulty 2/5 1-3 hours Newbie friendliness 61/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
external-issue to-triage
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
needs triage
Difficulty 1/5 Under an hour Newbie friendliness 88/100
homarr-labs/homarr#6976 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day