Skip to content

Translate frontend with i18next#164

Open
alex-ahumada wants to merge 9 commits into
GetDKAN:mainfrom
alex-ahumada:i18n
Open

Translate frontend with i18next#164
alex-ahumada wants to merge 9 commits into
GetDKAN:mainfrom
alex-ahumada:i18n

Conversation

@alex-ahumada

Copy link
Copy Markdown

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

dafeder commented Apr 18, 2022

Copy link
Copy Markdown
Member

Thank you @alex-ahumada! Will review ASAP

@alex-ahumada

Copy link
Copy Markdown
Author

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

@alex-ahumada

Copy link
Copy Markdown
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 dafeder requested a review from dgading May 8, 2024 19:47
@dafeder

dafeder commented May 8, 2024

Copy link
Copy Markdown
Member

@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
Copy Markdown
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