The change introduced in #418 broke an application for me. The reason seems to be that the translations table have not null constraints in the translatable attributes and after the change introduced any new empty translation is considered dirty and becomes a candidate to save in saveTranslations method.
Gummibeer
commented
3 months ago
The change introduced in #418 broke an application for me. The reason seems to be that the translations table have not null constraints in the translatable attributes and after the change introduced any new empty translation is considered dirty and becomes a candidate to save in
saveTranslationsmethod.