- 🇫🇷France andypost
There's a case when at least 2 themes are required - when you collect layouts from frontend (default theme) to display them as list at "manage display" pages (in admin theme)
Drupal\Core\Theme\Registry usually works like this:
We should remove all artifacts that suggest that Theme\Registry would support more than one theme:
$this->registry[$theme_name] becomes $this->registry.
$this->runtimeRegistry[$theme_name] becomes $this->runtimeRegistry.
$this->themeName should be initialized in $this->init().
$theme_name in $this->init() is redundant, and should be removed.
In a follow-up issue, we could make a proxy split, like so:
One class where $theme_name and $theme object are passed into the constructor.
This will contain most of the logic.
In this class we no longer need to worry about whether it has been initialized or not.
Another class which acts as a proxy layer, and which lazily creates the "real thing" when it is needed.
Active
10.1 ✨
Last updated
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
There's a case when at least 2 themes are required - when you collect layouts from frontend (default theme) to display them as list at "manage display" pages (in admin theme)