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

alexpott’s picture

Issue tags: +minor version target
Berdir’s picture

We 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.

alexpott’s picture

alexpott’s picture

Status: Active » Closed (duplicate)