rmariuzzo / Laravel-JS-Localization

🌐 Convert your Laravel messages and consume them in the front-end!
https://github.com/rmariuzzo/laravel-js-localization
MIT License
595 stars 171 forks source link

Separate each language folder #120

Open AliN11 opened 6 years ago

AliN11 commented 6 years ago

I think it is not possible to separate each language folder. For example I don't need Italian language while default locate is set to English. It could be a big issue if we have many languages and files.

I expect each language folder to be generated in separate file (not all languages in one file). something like this after generation:

en.js
fr.js
it.js
...
rmariuzzo commented 6 years ago

This sound like an interesting improvement for this library. Currently, we generate everything in one single file (unfortunately).

BTW, @AliN11 are you using webpack? If yes, check this: https://github.com/rmariuzzo/laravel-localization-loader/ it may help for you specific case. Otherwise, I will think of a solution for your particular case.

AliN11 commented 6 years ago

Yes I am using Webpack but didn't try given repository 😉. It would be great if you do something like this in config file:


return [
    'desired/path/for/english' => [
        'en/validation',
        'en/auth',
        'en/customers/profile',
        'en/somthingelse',
    ],
    'it' => [
        'it/validation',
        'it/auth',
    ],
];
kingvish commented 6 years ago

Another feature or complexity can be like I want to use this with modular project build with https://github.com/nWidart/laravel-modules, There is separate translation folder for each module.

ghost commented 6 years ago

I think this will definitely be a nice addition, it would bring further consistency with the Laravel Localization API.