-
We have three files that define backend routes: * Configuration/Backend/Routes.php * Configuration/Backend/AjaxRoutes.php * Configuration/Backend/Modules.php Routes defined by these files now contain the composer package name ('name' attribute in composer.json) of the package that defined the route as option. Backend modules now have a getPackageName() method. This is useful as shown with #96962 and will likely find further usages in the future. Change-Id: Ifa20f11ee7caa470eb2a1eed9e4ddf3ede088a54 Resolves: #96961 Related: #96962 Related: #96733 Releases: main Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/73191 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Oliver Bartsch <bo@cedev.de> Tested-by:
Benjamin Franzke <bfr@qbus.de> Reviewed-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Benjamin Franzke <bfr@qbus.de>
84ceebc2We have three files that define backend routes: * Configuration/Backend/Routes.php * Configuration/Backend/AjaxRoutes.php * Configuration/Backend/Modules.php Routes defined by these files now contain the composer package name ('name' attribute in composer.json) of the package that defined the route as option. Backend modules now have a getPackageName() method. This is useful as shown with #96962 and will likely find further usages in the future. Change-Id: Ifa20f11ee7caa470eb2a1eed9e4ddf3ede088a54 Resolves: #96961 Related: #96962 Related: #96733 Releases: main Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/73191 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Oliver Bartsch <bo@cedev.de> Tested-by:
Benjamin Franzke <bfr@qbus.de> Reviewed-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Benjamin Franzke <bfr@qbus.de>
Loading