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

Translate frontend with i18next #164

Open
wants to merge 9 commits into
base: main
Choose a base branch
from

Conversation

alex-ahumada
Copy link

Frontend translation using i18next , with browser language detection and EN/ES translations.
We should probably move translations from config file to individual language files when more languages are added.

resolves #78

@dafeder
Copy link
Member

dafeder commented Apr 18, 2022

Thank you @alex-ahumada! Will review ASAP

@alex-ahumada
Copy link
Author

Thanks @dafeder! We should remove debug from i18next config file before release.

@alex-ahumada
Copy link
Author

Codeclimete warns about: Similar blocks of code found in 2 locations. Consider refactoring.

That can't be fixed as i18next language config blocks are similar by design.

@dafeder
Copy link
Member

dafeder commented May 8, 2024

@alex-ahumada I know its been a while on these PRs but we do intend to get back to them soon. Not sure if you're able to update them so they merge cleanly again; I imagine your fork has diverged a bit but that would be helpful.

I'm sure we can override that codeclimate gate if that's the only blocker 😄

@alex-ahumada
Copy link
Author

I'll try update the fork and resolve the conflicts in the coming days @dafeder !

@dafeder dafeder requested a review from brdunfield May 14, 2024 20:20
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

Successfully merging this pull request may close these issues.

Frontend is not translatable
3 participants