Skip to content

fix: i18n hardcoded data issue

Issue Summary

Hardcoded strings present in application despite i18n implementation

Current Behavior:
Several components contain hardcoded UI strings instead of using i18n translation keys, causing test failures and inconsistent localization.

Expected Behavior:
All user-facing strings should be externalized and accessed via the i18n framework.

Problem Statement

  • Hardcoded text exists across multiple components
  • Breaks localization and causes automated test failures
  • Affects UI consistency and maintainability

Impact:

  • Failing test cases blocking commits
  • Inconsistent translations
  • Reduced scalability for multi-language support

Proposed Solution

  • Identify all hardcoded strings in the codebase
  • Replace with i18n translation keys
  • Update translation files
  • Refactor components to use translation functions (t('key'))
  • Update tests to match i18n-based rendering

Unit Test Requirements

Assertions:

  • Uses translation keys instead of hardcoded text
  • Renders correctly
  • Updates on language change
  • Handles missing keys gracefully

Definition of Done

  • All hardcoded strings removed
  • All UI text uses i18n
  • Tests passing
  • No UI regressions
  • Code reviewed and approved
  • Lint and format checks pass