Currently deleting a single config entity can result in the site's configuration being in an inconsistent state if it has configurations which rely on it.
Delete a configuration like a user role with the action module enabled, the role will be removed, but the relevant action configurations will still be left in the site even though they're hard dependencies on it.
Provide a new optional parameter to the ConfigDeleteInterface::delete method, which ensures that the entity's delete hooks are ran.
I'm aware that this is a major change in behaviour, so I've made it an opt-in behaviour instead for modules which require the new functionality.
N/A
ConfigDeleteInterface::delete method definition becomes:
- public function delete($type, $name);
+ public function delete($type, $name, $entity_delete = FALSE);
N/A
Fixed
2.0
Base module
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Issue #3218227: ConfigDeleteInterface::delete should allow ConfigEntity...
Automatically closed - issue fixed for 2 weeks with no activity.