fix/profile-locales-inconsistency #1026
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #1021
Title: Fix Translation Locale Inconsistencies: Migrate to Consistent profiles Naming Convention
Description:
This PR fixes the issue where different locale files were using different naming styles for profile-related translations (like PROFILE, PROFILES, and profiles). Because of this, some translations weren’t loading properly and a few components were throwing i18n errors.
To fix everything, I moved all profile-related translations into one consistent section called “profiles” (lowercase) across all languages. I also added a few missing keys (yourPassword, back, deleteForever, superAdmin) so every locale now has full coverage.
Changes made:
• Updated all locale files by renaming PROFILE/PROFILES to profiles
• Added the missing translations mentioned above
• Updated Vue components so they now point to the correct lowercase keys
• Made sure all 10 languages (EN, DE, FR, HI, JA, PT_BR, RU, ZH, AR, ES) have the same structure
Why this fix was needed:
• Some parts of the app were showing fallback text or missing translations
• Components like Profile and Account Delete flow were throwing i18n warnings
• The codebase was inconsistent and harder to maintain because of mixed naming conventions
• Using one clear lowercase structure makes everything cleaner and prevents future issues
Testing:
I tested the Profile screens in all languages and everything loads correctly now.
Account deletion shows the right text, the super admin panel doesn’t throw translation errors anymore, and there are no missing-key warnings in the console.
All JSON files also validate properly.
Changes Summary:
Modified: All locale JSON files to standardize “profiles” section
Modified: Components that referred to old keys
Added: yourPassword, back, deleteForever, superAdmin translations in all languages