[TASK] Deprecate second controller action argument
Core eid and backend dispatching uses only the $request object as argument, but not the prepared $response object anymore. This was a misconception in the first place. The patch deprecates the second argument and logs deprecations by reflecting the target action at runtime. This can be supressed with a new feature toggle. Resolves: #84196 Releases: master Change-Id: I003aba6010957cd82e6910fb718ef531116296be Reviewed-on: https://review.typo3.org/58190 Reviewed-by:Benni Mack <benni@typo3.org> Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de>
Showing
- typo3/sysext/backend/Classes/Http/RequestHandler.php 1 addition, 0 deletionstypo3/sysext/backend/Classes/Http/RequestHandler.php
- typo3/sysext/backend/Classes/Http/RouteDispatcher.php 32 additions, 3 deletionstypo3/sysext/backend/Classes/Http/RouteDispatcher.php
- typo3/sysext/core/Classes/Http/Dispatcher.php 34 additions, 5 deletionstypo3/sysext/core/Classes/Http/Dispatcher.php
- typo3/sysext/core/Classes/Http/DispatcherInterface.php 6 additions, 5 deletionstypo3/sysext/core/Classes/Http/DispatcherInterface.php
- typo3/sysext/core/Configuration/DefaultConfiguration.php 1 addition, 0 deletionstypo3/sysext/core/Configuration/DefaultConfiguration.php
- typo3/sysext/core/Configuration/DefaultConfigurationDescription.yaml 3 additions, 0 deletions...t/core/Configuration/DefaultConfigurationDescription.yaml
- typo3/sysext/core/Documentation/Changelog/master/Deprecation-84196-BackendControllerActionsDoNotReceivePreparedResponse.rst 55 additions, 0 deletions...-BackendControllerActionsDoNotReceivePreparedResponse.rst
Please register or sign in to comment