Required field validation with translatable plugin
Hi! When using the awesome spatie-translatable plugin i'm getting a weird behavior: if i set a field as required, it validates correctly the current language, but allows saving for the non-active languages even if the field is not filled in.
That's something weird in some use cases, since if i have set the field as required, it's probably required to be there in all languages. This because mostly problematic when used with title fields or slug fields, since they are used for routing and other essential part of applications that become broken for the non active languages.
Is this something that can be improved with a PR, like adding a configuration option for the plugin to decide if the validation error should be thrown anyway? I'm happy to contribute this, would love some "direction" though!
More details here:
https://github.com/filamentphp/filament/issues/10527
That's something weird in some use cases, since if i have set the field as required, it's probably required to be there in all languages. This because mostly problematic when used with title fields or slug fields, since they are used for routing and other essential part of applications that become broken for the non active languages.
Is this something that can be improved with a PR, like adding a configuration option for the plugin to decide if the validation error should be thrown anyway? I'm happy to contribute this, would love some "direction" though!
More details here:
https://github.com/filamentphp/filament/issues/10527
GitHub
Package filament/spatie-laravel-translatable-plugin Package Version 3.1.29 Laravel Version 10.39 Livewire Version 3.3.3 PHP Version 8.2 Problem description When creating a resource with a translata...
