Language Change Not Reflecting in Work and Home Tags in Address Section
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 66/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- internationalization, mobile-dev
Research direction
Reproduce the issue in the Enatega Multivendor Customer App by changing the language in Settings or Profile, then opening the address section. Start by tracing the Work and Home labels and the app's language-selection behavior. Done means both tags update correctly across the reported languages on iOS and Android.
Written by the indexing model from the issue text.
Description
Describe the bug
When changing the language in the Enatega Multivendor Customer App, the Work and Home tags in the address section do not update to the new language. This inconsistency can lead to confusion for users as these tags play a crucial role in identifying and differentiating between work and home addresses.
To Reproduce
Steps to reproduce the behavior:
Open the Enatega Multivendor Customer App.
Navigate to the Settings or Profile section where language settings are available.
Change the app language to a different language.
Go to the address section and observe that the Work and Home tags do not reflect the updated language.
Expected behavior
The Work and Home tags in the address section should dynamically change according to the selected language to provide a seamless and user-friendly experience.
Screenshots
image
Smartphone:
Device: iOS and android
Additional context
The issue is reproducible across multiple devices and operating systems.
Confirm if the issue persists in different languages to identify if it is language-specific or a general bug.
- 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 patriciaperez90/document-solution-application-react
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
All issues in patriciaperez90/document-solution-application-react
Similar issues
-
area: image-engine bug priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
snapotter-hq/SnapOtter#3885 ·
Maintainers usually reply within 1 day
-
Mend: dependency security vulnerability
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 3 days
-
pending triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
bug P3 UI/UX
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
openclaw/openclaw#182077 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day