- Issue created by @catch
- First commit to issue fork.
- 🇨🇭Switzerland berdir Switzerland
Stumbled over this as well, thanks to 📌 Aggregate cache operations per bin to allow for more specific asserts Active
The module weight is stable, unlike the active theme, it doesn't change at runtime. We can sort the whole component list once by module weight and then negotiate doesn't actually need to do any negotiation, it can just return the first. We might need a cache tag on config:core.extension in case a module weight changes.
Also didn't check tests yet nor did I properly inject the module extension list.