#111468Provide a way to shim site-set dependency resolution
Description
It is mentally very hard to work with site-sets. Switching from explicit to implicit ordering was a tough choice by TYPO3. I developed more than 100 TYPO3 websites and get stuck again and again, so maybe a little be too tough and it might be possible, that TYPO3 made a bad decision (or i am just way too stupid) and i would like to propose a way to mitigate the issues.
If an extension author would be able to “shim” the dependencies of third-party site-sets, it would be very easy to solve various dependency ordering issues. Just like it was added to various module loaders in the past, when we had the same problems with third-party-modules and the combination of those.
That could be done by providing a PSR-14 Event. I will try to replace the service class for now (to add the shimming for my use-case) but a generic way to improve interoperability between third-party site-sets and my own site-sets would be the preferred way.
Why a PSR-14 Event? Because it can be added without introducing any breaking change, so this could be backported to V14 and V13 as well. As alternative, Set Overrides could work but that would be a breaking change for a Major Release.
More information might be found here https://talk.typo3.org/t/site-sets-are-killing-me-dependency-ordering-hell/6738/2, where i initially reached out for help
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Fix this issue
Start the commit message of your patch with this. Add what the patch does, and the versions it goes to in "Releases:". How to create a patch
- Commit message
-
[FEATURE] Provide a way to shim site-set dependency resolution Resolves: #111468 Releases: main
History 1
-
Philipp Wrann changed description <span data-processor="relativetime" data-value="2026-11-17T13:22:34+00:00" > 11/17/26, 13:22 </span>