-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
Update the frontend to use i18n keys #4280
Comments
Went through the codebase and got a good understanding of the changes that I would need to make here. Can I work on this? Also what are your thoughts on adding eslint-plugin-i18n to give warnings so that we do not miss out on this in the future? |
Thanks for taking this up @Vaishakh-SM, feel free to open a PR with the changes when you're ready. As for |
Checklist:
|
Hey! I can assist with the i18n process if you want 💪 |
Hi @danicruz0415 ! Yea that'll be great. I've raised a PR where I've made changes to a single file. If that seems good we could start making changes to the entire repo. |
This issue is stale because it has been open for 30 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
This issue is stale because it has been open for 30 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
What problem or use case are you trying to solve?
The new UI hardcodes english text throughout the app. In order to support i18n, we should extend our i18n provider and replaced the hardcoded values with the new keys
Describe the UX of the solution you'd like
Do you have thoughts on the technical implementation?
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: