- 🇮🇳India nikunjkotecha India, Gujarat, Rajkot
This is more like image_widget_crop is not having proper format of data, I am happy to add the code but it should be marked as contrib module support (or category support)
Do you agree? If no, please share Drupal CORE example.
- 🇪🇸Spain omarlopesino
After reviewing this issue back, I agree that image_widget_crop is setting up "arbitrary properties" into the field value for convenience. That is the way the module is able to save the list of crops, to save it properly on entity save.
That is a specific behaviour that I think it won't be present on Drupal core, so I agree it belongs to contrib support.
However, I noticed something. This problem is happening because a contrib module is setting a property to a field value which won't be saved. In this case, that property won't be saved to database. I mean, if the entity is loaded, that `image_crop` property won't be present.
I will check if it is possible to solve this problem with other solution: loading the entity before saving the diff here, like it is done at entity update