Problem/Motivation

Install and uninstall is full of weird edge cases and need careful handling of services around container rebuilds. It would be great to refactor this process.

Steps to reproduce

Proposed resolution

Remaining tasks

Collect other installer related issues.

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet

Comments

nicxvan created an issue. See original summary.

alexpott’s picture

alexpott
he/they
Primary language English
Location 🇪🇺🌍
commented

I've been thinking that the main services should only get the kernel. And then they should use it trigger events via getting the event dispatcher from the kernel and then everything is always done with the correct services and container because the kernel is a synthetic service and is always the same object throughout the request / process - regardless of the number of rebuilds.

nicxvan’s picture

nicxvan commented

Oh that's a very interesting idea

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.

nicxvan’s picture

nicxvan commented
Issue summary: View changes

I wonder how we tackle this?

Both already get the kernel, do you think we start replacing pieces with an event?