marthaegrimaldi / marthaegrimaldi/food-ordering-application-using-react-native
Language Inconsistency in Enatega Multivendor Web for Restaurants with Variations
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Issue Summary:
When changing the language to Arabic in the Enatega Multivendor Web, a language inconsistency is observed for restaurants that offer menu variations. Specifically, the required tags, placeholders, and "Add to Cart" buttons associated with menu variations remain in English, causing a discrepancy in the translated content.
Steps to Reproduce:
Open the Enatega Multivendor Web.
Navigate to the language settings.
Change the language to Arabic.
Browse restaurants with menu variations.
Observe the required tags, placeholders, and "Add to Cart" buttons for menu variations.
Expected Behavior:
The required tags, placeholders, and "Add to Cart" buttons for menu variations should be translated into Arabic to provide a consistent and user-friendly experience in the selected language.
Actual Behavior:
The required tags, placeholders, and "Add to Cart" buttons for menu variations remain in English even after switching to Arabic, leading to a language inconsistency for users.
image
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.
Research direction
Start at the language settings and menu-variation UI entry points, then trace how required tags, placeholders, and Add to Cart buttons receive their text. Reproduce the issue in Arabic and verify that all three elements display Arabic translations while other languages remain unaffected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react-native
- Domain
- frontend, internationalization
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100