Code split enum files per translation with (dynamic) lazy load

[vpcvdc]

🚀 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.

[David]

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.