Multiple files per language about translate HOT 3 CLOSED

Not for the moment. I'm still investigating what is the easiest way to support file splitting and lazy loading. Mind that trying to split on per-component basis is opening a can of worms. At some point you may need to wait for numerous files downloaded just to show text correctly. Same for switching languages - there will be a performance/bandwidth penalty in this case.

from translate.

Well it would be practical to, at least, assign a separate .json translation file to each module in a large application, wouldn't you agree? Currently I am working on app with more than 30 modules, with lazy loading in place.

Keeping translation tokens in a single file per language would be a real nightmare. Setting some kind of resolve in routing data could possibly be a place of initiating a load of a new .json file (per currently active module).

I agree that keeping a single file per language is optimal with no loading overhead.

Btw, congrats on this cool library :).

from translate.

@micobarac yes, I fully agree that it lacks the per-module splitting and elaborating on that. thanks for the feeback :)

from translate.