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

Support i18n/<lang>.json naming #272

Open
2 tasks
mcm1957 opened this issue Dec 9, 2024 · 2 comments
Open
2 tasks

Support i18n/<lang>.json naming #272

mcm1957 opened this issue Dec 9, 2024 · 2 comments

Comments

@mcm1957
Copy link

mcm1957 commented Dec 9, 2024

Please implement support for i18n/.json naming

  • npm run translate should detect whether admin/i18n/{lang}/translations.json or admin/i18n/.json format is used at a repo and use or create the corrrect files for this naming format

  • npm run translate should provide an option to migrate form i18n/{lang}/translations.json to i18n/{lang}.json format. If reverse is required too should be discussed

@hombach
Copy link
Contributor

hombach commented Dec 15, 2024

great point Martin!
detection of the more developer friendly en.json instead of en\translation.json would be great!

Personaly I don't think that a migration-tool is necessary.

@UncleSamSwiss
Copy link
Collaborator

#281 Adds support for the new path and uses it as default path.
I'm not sure if we need to implement a migration tool. If the user wants to change it, they can do this manually.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants