I have used this repository to store multi-language data in JSON datatype. After switching from the base plugin to this repository, I encountered an issue with the locale switch.
Steps to Reproduce:
Add a translation field with required validation.
Enter data in the default language (in my case, English).
Save the data to ensure it is stored.
Switch to another language using the locale switcher option.
Switch back to English.
At this point, the data from the English field is lost, resulting in a validation error.
In v3.2.81, translatable models with a relationship to another translatable model don't get that relationship's data updated on locale change via the language switch.
Expected Behavior:
It should switch to the translated version of the content for that relationship
\App\Models\Overrides\Page extends \Z3d0X\FilamentFabricator\Models\Page and uses \RalphJSmit\Laravel\SEO\Support\HasSEO as well as Spatie\Translatable\HasTranslations (NB: the seo property is not part of the $translatable array since it's a relationship and not a db column)
\App\Models\Overrides\SEO extends \RalphJSmit\Laravel\SEO\Models\SEO and uses Spatie\Translatable\HasTranslations
\App\Filament\Resources\PageResource extends \Z3d0X\FilamentFabricator\Resources\PageResource, uses Filament\Resources\Concerns\Translatable and all related pages are properly overridden and configured
A (filament) section for the seo relationship is displayed on the (edit or create) page, its translatable attributes are editable thanks to the section's schema