-
Notifications
You must be signed in to change notification settings - Fork 179
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Code split enum files per translation with (dynamic) lazy load #250
Comments
Hi @vpcvdc, would you mind clarifying what you're asking for? At the moment, it's already possible to dynamically load translations on the fly on the clientside by customizing the hooks to fetch translation payloads. So I'm not sure what else you have in mind with in this feature proposal. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
馃殌 Feature Proposal
Thank you for amazing library.
Code split enum files per translation with (dynamic) lazy load feature.
Motivation
Above feature already there for translation. It's better to have it in enums as well.
Example
Enums for all world data (countries, states, districts) per translation file will be huge. Lazy load will be better for this case.
The text was updated successfully, but these errors were encountered: