- 🇳🇿New Zealand quietone
This is documented at Defining a plugin instance → , which is for using attributes.
#7 explains that this is to document best practice, not to enforce a change in core or elsewhere. Therefor, I think this can be closed.
Most plugin types that are discovered through class annotations live in ./src/Plugin/$vendor/$pluginType directories within modules. Some live in directories that do not have those two variable components, such as actions which live in ./src/Plugin/Action. This is not a bug, but it does prevent us from adding more plugin types to the action vendor in the future.
Document that ./src/Plugin/$vendor/$pluginType is the preferred (but not required) location for non-core plugins to preserve forwards compatibility.
None.
None, but modules may have to move plugins to a different namespace/directory.
Closed: outdated
11.0 🔥
plugin system
Primarily changes documentation, not code. For Drupal core issues, select the Documentation component instead of using this tag. In general, component selection is preferred over tag selection.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
This is documented at Defining a plugin instance → , which is for using attributes.
#7 explains that this is to document best practice, not to enforce a change in core or elsewhere. Therefor, I think this can be closed.