Follow-up to:
#1331486: Move module_invoke_*() and friends to an Extensions class
#1893680: Rename 'module_handler' service and ModuleHandler classes

Problem

  • module_enable(), module_disable(), module_set_weight(), etc have been left out from the ModuleHandler service, since it deals with "enabled" (active) modules only.

Goal

  • Move those extension management functions into a proper service.

Details

  • These functions are responsible for changing which extensions are participating in the application.
  • DrupalKernel contains some similar functionality already, but moving these functions directly onto DrupalKernel would result in infinite recursion.

Comments

catch’s picture

catch
he/him
Primary language English
commented

There's a circular dependency here in that these functions depend on drupal_*_schema_*() which in turn depend on hook_schema()/hook_uninstall() etc. which in turn depends on the hook system. We may need a service which only deals with $module.install hooks (which have a different execution path anyway) to break that dependency.

drupal_*_schema_*() also depends on the db_*() schema manipulation wrappers. I've opened an issue to discuss removing those at #1894396: Mark db_*() wrappers in database.inc as @deprecated for 9.x although an injected database object would be enough in this issue.

sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Status: Postponed » Active
dawehner’s picture

dawehner
Primary language German
commented
Issue summary: View changes
Status: Active » Fixed

... the module installer.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.