- Issue created by @jurgenhaas
The action plugins are all derived from HttpServiceApiHandlerInterface modules, but they don't declare the dependency upon those sources. That leads to the problem that anything that uses those action plugins will fail, if the source of the used plugins is being uninstalled and/or removed. I just got hit by that in the ECA context. Not sure if anything else is using those actions apart from maybe custom code. But there, the problem could be the same.
By implementing the calculateDependencies
in the action plugins, Drupal would take care that the sources of those plugins can't be disabled while at least one of their plugins is still in use somewhere.
Active
10.0
Code