Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

directory organization / recursive directory scan?

See original GitHub issue

In large projects with lots of localized strings, having just 1 file for all the translations per language gets hard to manage. How should I split and organize my locale files to better work on them? I see that this tool doesn’t support merging more that one locale file (which I think would be the first requirement), which would allow things like:

| - locales\
| ---- admin\
| -------- en.json
| -------- es.json
| ---- frontend\
| -------- en.json
| -------- es.json
| ---- mobile\
| -------- en.json
| -------- es.json

Issue Analytics

State:
Created 8 years ago
Reactions:2
Comments:19 (9 by maintainers)

Top GitHub Comments

1reaction

mogadanezcommented, Jan 28, 2019

Hi,

I have another structure comes from another projects which I want to reuse,

| - locales
|---en
| -----common.json
| -----specific.json
|---de
| -----common.json
| -----specific.json

is it possible to load such structure? can middleware helps in it?

0reactions

mashpiecommented, Jul 21, 2016

this is how test cover autoreload. Check out https://github.com/mashpie/i18n-node/blob/master/test/i18n.configureAutoreload.js to get an idea. It’s basically accomplished by configure autoreload and write json files after startup.

I’ll take a dive into module manager… looks promising 😃