By amateescu on
Change record status:
Published (View all published change records)
Project:
Introduced in branch:
8.7.x
Introduced in version:
8.7.0
Issue links:
Description:
Config entities have had a baked-in concept of synchronization since Drupal 8.0.0, and it is used to inform hook implementations that the entity is being changed as part of a config import process.
This functionality has been abstracted into a generic SynchronizableInterface interface and a default implementation has been added to all content entities.
If you are writing code that responds to a change in an entity (insert, update, delete, presave, etc.), and your code would result in a further change to the entity itself, you need to check and see if the original changes to the entity are part of a synchronization process, and skip executing your code if that is the case.
Impacts:
Module developers
