After #2926068: Deprecate system_rebuild_module_data() and remove usages in core, a new ModuleExtensionList argument to the \Drupal\Core\Config\ConfigImporter constructor is introduced and made optional for BC reasons. The old method signature was deprecated in that issue as the "optionalness" will be removed in Drupal 9.0.0

This issue is where the removal will be done in D9.

@param \Drupal\Core\Extension\ModuleExtensionList|null $extension_list_module
+   *   The module extension list. This is left optional for BC reasons, but the
+   *   optional usage is deprecated and will become required in Drupal 9.0.0.

Comments

almaudoh created an issue. See original summary.

andypost’s picture

andypost
he/him
Primary language Russian
commented
Related issues: +#3017360: Replace theme handler with theme installer in ConfigImporter

Better to combine this with related #3017360: Replace theme handler with theme installer in ConfigImporter

berdir’s picture

berdir
Primary language German
Location Switzerland
commented

I don't think we need dedicated issues for each case, we have dozens of those option arguments, one meta should be enough and we can then still decide if/how to split it up?

Version: 9.x-dev » 9.0.x-dev

The 9.0.x branch will open for development soon, and the placeholder 9.x branch should no longer be used. Only issues that require a new major version should be filed against 9.0.x (for example, removing deprecated code or updating dependency major versions). New developments and disruptive changes that are allowed in a minor version should be filed against 8.9.x, and significant new features will be moved to 9.1.x at committer discretion. For more information see the Allowed changes during the Drupal 8 and 9 release cycles and the Drupal 9.0.0 release plan.

berdir’s picture

berdir
Primary language German
Location Switzerland
commented
Status: Active » Closed (duplicate)

I'll remove it in #3104307: Remove BC layers in various Drupal\Core components