Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Problem/Motivation
#2260457: Allow config entities to remove dependent configuration keys when dependencies are deleted due to module uninstall introduces the ability for configuration entities to manage what happens when their dependencies are removed. We could generalise this to replace the custom code in FieldConfig::postDelete. This also means that configuration entities no longer will need to extend their reach to update other configuration entities.
Proposed resolution
tbd
Remaining tasks
patch
review
User interface changes
none
API changes
hopefully none
Comments
Comment #1
alexpottComment #2
BerdirWe could possibly add a list of config that depends on a given config entity into the standard delete form once #1728804: Introduce (Content)EntityDeleteForm and children to handle entity deletions is in.
Comment #3
alexpottI've possibly opened a dupe :) #2416409: Delete dependent config entities that don't implement onDependencyRemoval() when a config entity is deleted
Comment #4
alexpottClosing in favour of #2416409: Delete dependent config entities that don't implement onDependencyRemoval() when a config entity is deleted
Comment #5
alexpott