Skip to content
This repository has been archived by the owner on Nov 18, 2024. It is now read-only.

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

Open
vpcvdc opened this issue Aug 5, 2021 · 1 comment
Open

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

vpcvdc opened this issue Aug 5, 2021 · 1 comment

Comments

@vpcvdc
Copy link

vpcvdc commented Aug 5, 2021

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

@kayhadrin
Copy link
Contributor

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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants