dynamic languages about laravel-translatable HOT 8 CLOSED

I agree with @sdebacker, you can do whatever you want with Config::set('app.locales', []), preferably in a service provider.

Sorry but your use case is too specific to be included in this package. Feel free to create an extension or something.

Cheers :)

from laravel-translatable.

Why not use Config::set('app.locales', […]) somewhere in your app ?

from laravel-translatable.

What I'm suggesting is having more flexibility. Both the current option + a dynamic option. Where you can even have 'active' languages, those that can be disabled in the backend of an application for instance.

I would suggest normalising, as in using a 'language_id' in models to pinpoint to specific languages, this would also help in cascading deletion where if you delete a language, all models pertaining to said language would also be deleted.

from laravel-translatable.

One reason I like this package is that it's small with one responsibility. Perhaps making another package that extends laravel-translatable should make sense ? What do you think ?

from laravel-translatable.

Fair point, Then I would suggest events for this package for easy hooking...I would gladly create this package.

from laravel-translatable.

Is it really so specific though? Normalising the languages to a database? Ill be writing a package to extend this one but still

from laravel-translatable.

By adding the languages to the database you add extra complexity which is rarely needed. Let's keep the package simple and open for extension.

from laravel-translatable.

@wisepotato If you are still looking for a solution for your problem or someone in the future will look, you can see my fork: https://github.com/daverdalas/laravel-translatable

from laravel-translatable.