Improve Developer Experience for i18n Configuration

[gigincg]

Objective

Enhance the developer experience when working with internationalization (i18n) in Care by consolidating locale files and implementing a VS Code extension for easier management of translations.

Tasks

• Merge Multiple JSON Files into One File per Locale

  • Combine all separate JSON files (e.g., Bed.json, User.json, etc.) into a single file for each locale.
  • Example: Create en.json, es.json, etc., containing all translations for each language.
  • Update the i18n configuration to use these consolidated files.

• Improve Dev Experience for i18n Management

  • Explore existing extensions or consider building a VS Code extension with the following features:
    a. Quick search for existing translations within the current locale file.
    b. Easy creation of new translation keys directly from the code editor.
    c. Automatic insertion of newly created keys into the appropriate locale file(s).

Acceptance Criteria

• All locale-specific JSON files are consolidated into single files per language.
• Enables quick search of existing translations.
• Enables creation of new translation keys from codebase (JSX files).
• Documentation is updated to reflect the new i18n workflow.

Additional Notes

• Consider using a tool like i18next-parser to automatically extract translation keys from the codebase.

[anandaashish74711]

@gigincg i want to work on this issue .could you please assign me this task?

[gigincg]

@anandaashish74711 We have moved to i-8n ally to solve this.

If you have a better solution, please suggest your solution here. Happy to assign the issue if a better solution is available

[i0am0arunava]

@gigincg ,I saw someone is working on the point 1 of Task ,can I start to work on the point 2 (vs code extension)

[gigincg]

@i0am0arunava Please read through all comments in an issue when you have intent to take it up.

Task 2 has been solved with i18n ally. You need to comment a better solution if you want to take it up.

Personal Note: This is issue requires a bit of research and is better suited for a seasoned dev.