Contrib.social

Should TypedConfigManager::getFallbackName() support plugin derivatives whose IDs are not delimited with a colon?

Open on Drupal.org →
Created on 11 August 2014, over 10 years ago
Updated 25 March 2025, 8 days ago

Problem/Motivation

  • In #2317865: Config schema definitions for plugins aren't applied to their derivatives → , we're making TypedConfigManager::getFallbackName() split on colons (:) in addition to dots (.), so that the schema of a derived plugin can fallback to its base plugin's schema in the same way that the schema of a config entity can fallback to the schema of its entity type.
  • However, in #2317865-24: Config schema definitions for plugins aren't applied to their derivatives → , neclimdul pointed out that the IDs of derived plugins can be constructed in alternate ways than delimiting with a colon. If any plugins use some alternate approach, then currently, they don't benefit from the above schema fallback logic.
  • There are no core uses of plugin derivatives using such an alternate ID construction.
  • For a contrib plugin type to use an alternate construction, it would need to a) make the plugin manager use an alternate derivative discovery decorator than DerivativeDiscoveryDecorator (it could subclass that one and override encodePluginId() and decodePluginId()), and b) make the plugin base class override getBaseId() and getDerivativeId().
  • It's not really clear what the motivation would be, if any, for a contrib plugin type to want to use an alternate ID pattern for its plugins' derivatives.

Proposed resolution

?

Remaining tasks

  • Decide whether to allow extensibility of TypedConfigManager::getFallbackName() to handle additional replacement patterns.
  • If so, then figure out how to implement that extensibility.

User interface changes

None

API changes

?

✨ Feature request
Status

Postponed: needs info

Version

11.0 🔥

Component

configuration system

Created by

🇺🇸United States effulgentsia

Live updates comments and jobs are added and updated live.
  • stale-issue-cleanup

    To track issues in the developing policy for closing stale issues, [Policy, no patch] closing older issues

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.

  • Comment 8 days ago →
    🇺🇸United States smustgrave

    Thank you for sharing your idea for improving Drupal.

    We are working to decide if this proposal meets the Criteria for evaluating proposed changes. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or there is no community support. 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!

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024