- ๐ฌ๐งUnited Kingdom catch
#2702061-106: Unify & simplify render & theme system: component-based rendering (enables pattern library, style guides, interface previews, client-side re-rendering) โ and downwards is relevant, but the most likely outcome would be that the number of different elements is reduced, and eventually #theme gets dropped in favour of #type component, but don't really see any reason that this couldn't all be worked on in parallel without explicit dependencies.
- ๐ฆ๐บAustralia larowlan ๐ฆ๐บ๐.au GMT+10
Yes, agree #142 is nicer and it also gels with some thinking I had in this experiment
It also means we might not have to add new classes for everything, we could possibly use the existing render element plugins but instantiate them.
- ๐บ๐ธUnited States nicxvan
I've been eyeing ๐ Extension System, Part IV: Properly register all installed extensions/namespaces during container generation Needs work because it's likely on the road to getting oop hooks in themes which will let us clean up a fair bit around preprocess.
- First commit to issue fork.
- ๐ฆ๐บAustralia dpi Perth, Australia
Created a autoloading-related issue for ensuring classes are added to the autoloader before container cache is unserialized @ ๐ Using instances of classes defined by modules in service container parameters causes fatal errors Active