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.

Sign up for GitHub

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

Jump to bottom

Split translations by component #4411

Closed
susnux opened this issue Aug 11, 2023 · 2 comments · Fixed by #4861
Closed

Split translations by component #4411

susnux opened this issue Aug 11, 2023 · 2 comments · Fixed by #4861
Labels
enhancement New feature or request

Comments

@susnux
Copy link
Contributor

susnux commented Aug 11, 2023

I think it would be nice if we could split translations by components when building, that way not every string for even unused components end up in you bundle.

cc @ShGKme
@susnux susnux added the enhancement New feature or request label Aug 11, 2023
@ShGKme
Copy link
Contributor

ShGKme commented Aug 16, 2023

Hmm, I didn't notice before that components with translations have all library translations.

Indeed, if t is imported once in the component, then all the translations to all supported languages for all components are included:

image

@ShGKme
Copy link
Contributor

ShGKme commented Aug 16, 2023 •
edited

Currently, we have 88 keys in translations in 106 languages which result in ~10_000 lines in each component with translations and it is really a lot.

@susnux susnux mentioned this issue Nov 21, 2023
Merged
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
2 participants
@susnux @ShGKme