91000[!!!][FEATURE] Introduce submodule dependencies for backend modules
Commit message
Review
-
Code review CR +2 Done
- Oli Bartsch +2
- Stefan Bürk +1
- Benni Mack +1
-
Verified V +2 Done
- Oli Bartsch +2
- Stefan Bürk +1
- Benni Mack +1
- core-ci +1 CI
Issues 1
Files 10
- typo3/sysext/backend/Classes/Module/BaseModule.php+10 −0
- typo3/sysext/backend/Classes/Module/MenuModule.php+5 −0
- typo3/sysext/backend/Classes/Module/ModuleInterface.php+6 −0
- typo3/sysext/backend/Classes/Module/ModuleProvider.php+31 −0
- typo3/sysext/backend/Resources/Private/Language/Modules/about.xlf4+6 −0
- typo3/sysext/backend/Resources/Private/Partials/About/Modules.html+33 −16
- typo3/sysext/backend/Tests/Functional/Module/ModuleProviderTest.php+158 −0
- typo3/sysext/core/Documentation/Changelog/14.0/Breaking-107663-NewMethodInModuleInterface.rstnew+56 −0
- typo3/sysext/core/Documentation/Changelog/14.0/Feature-107663-DependsOnSubmodulesOptionForModules.rstnew+74 −0
- typo3/sysext/info/Configuration/Backend/Modules.php+1 −0
Review log 1316
-
Oli Bartsch uploaded patch set 1 10/10/25, 15:48
-
core-ci voted on patch set 1 V +1 10/10/25, 15:59 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/86418
-
Josua Vogel commented on patch set 1 10/11/25, 15:06
about.xlf:106```suggestion <source>There are currently no functions available for the %1s module.</source> ``` -
Oli Bartsch commented on patch set 2
V +110/13/25, 05:56Published edit on patch set 1. -
core-ci voted on patch set 2 V +1 10/13/25, 06:02 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/86512
-
Josua Vogel commented on patch set 2 10/13/25, 07:10
about.xlf:103ReplyDoneabout.xlf:106ReplyDone -
Benni Mack voted on patch set 2 CR +1 V +1 10/13/25, 15:29
-
Stefan Bürk commented on patch set 2 10/13/25, 16:17
The ModuleInterface itself is not internal .. should that not be considered public API then ? If yes, this would be a breaking change adding the new function to the interface and requires at least a breaking rest file along with the feature restfile stating the migration path for custom module implementations, adding the method to the module without a effect in v13 but satisfying the interface on an upgrade. Or am I wrong ? -
Oli Bartsch uploaded patch set 3
CR +1V +110/13/25, 21:06 -
Oli Bartsch commented on patch set 3 10/13/25, 21:08
Reply
I don't get the relation to v13 as this is main only, however I've added a breaking rst with a migration path. -
core-ci voted on patch set 3 V +1 10/13/25, 21:14 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/86580
-
Stefan Bürk commented on patch set 3 CR +1 V +1 10/13/25, 21:42
Reply
Sure, this is breaking. But in case someone has a dual coreversion extension (v13 & v14) they could add the new method to the custom module .. in v13 without effect, in v14 satisfying the interface. Maybe it's just me having a couple of extensions in the company following dual core version supports (albeit no one having a custom module based on the interface). Thanks for adding the rest file. -
Benni Mack voted on patch set 3 CR +1 V +1 10/14/25, 08:39
-
Oli Bartsch voted on patch set 3 CR +2 V +2 10/14/25, 08:40
-
Oli Bartsch merged patch set 4 10/14/25, 08:40
-
Lina Wolf commented on patch set 4 10/17/25, 08:03
Unresolved
Please review related documentation changes: https://github.com/TYPO3-Documentation/TYPO3CMS-Reference-CoreApi/pull/6105
about.xlf:103