@bkintanar This looks like a nice addition. Any reasons to not merge this?
As far as I know, all frontend fields use the Vue translation helpers. Loading translations from a vendor-override location would enable users to keep translations for advanced-nova-media-library separate from their other lang files. Giant JSON files tend to become messy string graveyards otherwise 😄
The approach in this PR is similar to how Nova itself does it (vendor/laravel/nova/src/NovaServiceProvider.php::registerResources). I'd suggest using lang_path instead of resource_path('lang/') though, this helper is available in laravel/framework8.x and up.
@bkintanar This looks like a nice addition. Any reasons to not merge this?
As far as I know, all frontend fields use the Vue translation helpers. Loading translations from a vendor-override location would enable users to keep translations for
advanced-nova-media-libraryseparate from their other lang files. Giant JSON files tend to become messy string graveyards otherwise 😄 The approach in this PR is similar to how Nova itself does it (vendor/laravel/nova/src/NovaServiceProvider.php::registerResources). I'd suggest usinglang_pathinstead ofresource_path('lang/')though, this helper is available inlaravel/framework8.x and up.