Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE] - improve handling of Apps translations terms #211

Open
cedricfrancoys opened this issue Jan 7, 2025 · 0 comments
Open

[FEATURE] - improve handling of Apps translations terms #211

cedricfrancoys opened this issue Jan 7, 2025 · 0 comments
Labels
feature New feature or request

Comments

@cedricfrancoys
Copy link
Collaborator

Current Setup

Currently, there is a single translation file per language located in:

/public/assets/i18n

This file is part of the initialization files for the core package.

Requirements

  1. Package-Specific Translation Files:
    Each package should define its own translation constants in its directory:

    init/assets/i18n
    
  2. Dynamic Enrichment of Global Translation Files:
    During the initialization of a package:

    • The translation files in /public/assets/i18n should be dynamically enriched with the content from the package-specific files.

Process

For each file in init/assets/i18n:

  • Locate the corresponding file in /public/assets/i18n.
  • Perform the following steps:
    1. Extract the existing translations from the file in /public/assets/i18n.
    2. Merge the translations from the package-specific file into the existing content.
    3. Store the merged content back into the original JSON file.
@cedricfrancoys cedricfrancoys added the feature New feature or request label Jan 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
Status: No status
Development

No branches or pull requests

1 participant