08-Project-Health / 08.08.Fix-Languages-Switch

08.08.Fix Languages Switch

08.08. Fix Languages Switch

1. Problem Analysis

Users experience "semi-English" content when switching languages (e.g., to Finnish or Swedish) on the Report Dashboard.

Root Causes:

• Missing Translation Keys: The apiValues section in en.json contains a comprehensive list of technical field labels (e.g., Sentry Mode, Dashcam State) that are missing in fi.json, sv.json, and other locale files.
• Fallback Mechanism: vue-i18n is configured to fall back to en when a key is missing, causing these technical fields to appear in English.
• Untranslated API Values: Some values returned from the Tesla API (e.g., color names like DeepBlue, state names like OWNER) are being rendered directly or are not mapped in the translateApiValue helper.

2. Implementation Steps

Step 1: Locale Parity Sync

• Task: Ensure all .json files in src/vue/app/src/i18n/locales/ have the exact same key structure as en.json.
• Specific Focus: The apiValues object, including fieldLabel, panelTitle, chapterTitle, and boolean sections.

Step 2: Technical Field Translations

• Task: Translate the newly added keys in all languages.
• Target Fields:
  • Make, Model, Model Year, Vehicle Name
  • Region, Software Version
  • Security and Presence, Controls and Driving, Diagnostics and Limits
  • Access Type, Supercharging, Charge Port Type
  • Exterior Color, Wheel Type, Roof Color

Step 3: Enhance translateApiValue Helper

• Location: src/vue/app/src/components/ReportDashboard.vue
• Task: Update the apiSections array to include more categories from the locale files.
• New Categories to Add:
  • apiValues.exteriorColor (e.g., DeepBlue -> Syvänsuininen)
  • apiValues.accessType (e.g., OWNER -> Omistaja)
  • apiValues.wheelType
  • apiValues.trimBadging

Step 4: Update Global Vocabulary

• Task: Ensure all values used in ffPanel and ffRows helpers are passed through translateLabel and translateApiValue correctly.

3. Verification & Testing

3.1 Automated Tests

• Update Test: Modify bnc-cpt-wui/src/nodejs/the-bot/test/test-104.i18n-completeness/test-104.i18n-completeness.spec.js.
• Improvement: Instead of a hardcoded KNOWN_KEYS list, the test should dynamically load en.json and verify that every key exists and has a unique value in fi and sv.

3.2 Manual Verification

1. Open the application locally.
2. Navigate to a generated report.
3. Cycle through all 9 supported languages.
4. Verify that sections like "Vehicle Identity", "Security", and "Technical Specifications" are fully translated.

4. Deployment

Once verified locally: 1. Run ENV=prd ./run -a do_gcp_deploy_wui to push changes to production. 2. Clear browser cache or check in Incognito mode to bypass CDN caching of old JSON files.