The ConfigInstaller should add a dependency on the extension used to install the configuration

Created on 28 March 2015, over 9 years ago
Updated 30 January 2023, almost 2 years ago

Extensions can provide configuration that has no dependency on itself - eg. the Book node type in the Book module. We ensure a dependency by adding an enforced dependency. This is done manually. However, users have the general expectation that configuration in config/install and config/optional should depend on the module that provides in. This would help solve current bugs like #2459619: migrate_drupal cannot be uninstalled and reinstalled β†’ and some of the issues raised on #2431157-3: Review PreExistingConfigException special casing for install profile β†’ and #2460529-20: Migrations need to use the configuration entity dependency system β†’ .

The config/optional is going to be tricky to solve :(

πŸ“Œ Task
Status

Needs work

Version

10.1 ✨

Component
ConfigurationΒ  β†’

Last updated 3 days ago

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.

  • The Needs Review Queue Bot β†’ tested this issue. It either no longer applies to Drupal core, or fails the Drupal core commit checks. Therefore, this issue status is now "Needs work".

    Apart from a re-roll or rebase, this issue may need more work to address feedback in the issue or MR comments. To progress an issue, incorporate this feedback as part of the process of updating the issue. This helps other contributors to know what is outstanding.

    Consult the Drupal Contributor Guide β†’ to find step-by-step guides for working with issues.

Production build 0.71.5 2024