Documentation in ConfigDependencyManager conflates plugin dependencies and config dependencies making it confusing

Created on 21 October 2014, over 9 years ago
Updated 31 August 2023, 10 months ago

Problem/Motivation

 * Classes for configurable plugins are a special case. They can either declare
 * their configuration dependencies using the calculateDependencies() method
 * described in the paragraph above, or if they have only static dependencies,
 * these can be declared using the 'config_dependencies' annotation key.

This is does not really tell the whole story. The configuration entity has to implement EntityWithPluginCollectionInterface and the plugins can implement ConfigurablePluginInterface. If the config entity implements EntityWithPluginCollectionInterface plugin providers and dependencies declared in the plugin's config_dependencies definition key (this does not have to be an annotation - it can be a derived definition) are added. If the plugin implements ConfigurablePluginInterface then each plugin instance's calculateDependencies() method is called.

Steps to reproduce

Proposed resolution

See #4

Remaining tasks

Update the patch. This is a patch so stay with a patch, not an MR
Review

User interface changes

API changes

Data model changes

Release notes snippet

🐛 Bug report
Status

Needs work

Version

11.0 🔥

Component
Documentation 

Last updated about 15 hours ago

No maintainer
Created by

🇬🇧United Kingdom alexpott 🇪🇺🌍

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.69.0 2024