Factor getConfig(), setConfig(), getConfigDefinition(), and getConfigDefinitions() out of ExecutablePluginBase

Created on 19 February 2013, almost 12 years ago
Updated 16 January 2025, 5 days ago

Follow up from #1743686: Condition Plugin System β†’ . getConfig() and setConfig() are useful for all plugins where configuration needs to be gotten or set after plugin instantiation. getConfigDefinition() and getConfigDefinitions() are useful for all plugins that want to support configuration introspection UIs and APIs (like Rules does). None of this is specific to "executable" plugins.

This is also a good issue to further discuss the difference between runtime swappable configuration and context, since these methods currently overlap quite a bit with the various context related ones. In Rules, there is no difference. But in Blocks, there is. There's a little discussion of this in the original issue, but I'm not up to speed enough on it to summarize that here. Someone who is: please do.

πŸ“Œ Task
Status

Postponed: needs info

Version

11.0 πŸ”₯

Component

plugin system

Created by

πŸ‡ΊπŸ‡ΈUnited States effulgentsia

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.

  • πŸ‡ΊπŸ‡ΈUnited States smustgrave

    Thank you for creating this issue to improve Drupal.

    We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for 8+ years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.

    Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

    Thanks!

Production build 0.71.5 2024