+1
ajfernandez → created an issue.
Hello everyone.
I am having the same need as @edurenye in a project. The user needs to know which fields are mandatory, and the translation work must be able to be validated by leaving optional fields empty, since it could happen that the user wants the content in a specific language to not have data in such fields.
I am attaching here the updated patch to work with the latest stable version of the module (8.x-1.15).
ajFernandez → created an issue.
Hello everyone.
I am having the same problem in a project. I have applied the MR code in my project and can confirm that it works correctly.
Perhaps, as @berdir comments, it would be more complete by adding some configuration setting in the module to enable this functionality, or perhaps even at the translation job level, to decide whether to apply this configuration individually in each translation job.
jlbellido → credited ajFernandez → .
ajFernandez → created an issue.