Currently, container rebuild and flushing all caches is done with procedural functions
drupal_rebuild(), drupal_flush_all_caches(), _drupal_flush_css_js().
In
📌
Convert drupal_rebuild() and drupal_flush_all_caches() functions into cache Rebuilder class
Needs work
it is being proposed to convert these to a cache rebuilder class.
However, this still leaves a hard-coded piece of code to do all the tasks needed on container rebuild.
As an alternative, I propose to introduce events to decentralize these tasks.
(in fact this is not mutually exclusive with the cache rebuilder class)
Introduce one event for "container rebuilt".
Introduce another event for "all caches should be cleared".
Add a subscriber for "container rebuilt" that triggers the "all caches should be cleared" event.
Let different services subscribe to these events.
Active
11.0 🔥
Last updated
Actually the hard-coded version as in drupal_flush_all_caches() has one advantage:
The order is fully predictable, without using weights.
Let's go ahead splitting it up, and see later how we like it.