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

Follow the conventions of i18n by adding one JSON per language #369

Open
AerunDev opened this issue Jul 21, 2024 · 0 comments
Open

Follow the conventions of i18n by adding one JSON per language #369

AerunDev opened this issue Jul 21, 2024 · 0 comments
Assignees
Labels
technical story Issues related to technical work

Comments

@AerunDev
Copy link
Collaborator

As a Developer
I would like to use one big JSON per language
So that I'm following the i18n good practices

@AerunDev AerunDev added the technical story Issues related to technical work label Jul 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
technical story Issues related to technical work
Projects
Status: In Progress
Development

No branches or pull requests

2 participants