You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 18, 2024. It is now read-only.
Hi @vpcvdc, would you mind clarifying what you're asking for?
Would you be able to explain it with a more practical example?
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 freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
🚀 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: