[TASK] Avoid implicitly nullable class method parameter in `EXT:reports`
With PHP 8.4 marking method parameter implicitly nullable is deprecated and will emit a `E_DEPRECATED` warning. One recommended way to resolve this, is making it explicitly nullable using the `?` nullable operator. [1] This prepares the way towards PHP 8.4 compatibility. [1] https://php.watch/versions/8.4/implicitly-marking-parameter-type-nullable-deprecated Resolves: #104206 Releases: main, 12.4, 11.5 Change-Id: I0d82e0474143f63870f772002de52d26c6c960fd Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84908 Tested-by:Stefan Bürk <stefan@buerk.tech> Tested-by:
Oliver Klee <typo3-coding@oliverklee.de> Reviewed-by:
Stefan Bürk <stefan@buerk.tech> Tested-by:
core-ci <typo3@b13.com> Reviewed-by:
Oliver Klee <typo3-coding@oliverklee.de>
Showing
- typo3/sysext/reports/Classes/Report/Status/SecurityStatus.php 1 addition, 1 deletion...3/sysext/reports/Classes/Report/Status/SecurityStatus.php
- typo3/sysext/reports/Classes/Report/Status/Status.php 2 additions, 2 deletionstypo3/sysext/reports/Classes/Report/Status/Status.php
- typo3/sysext/reports/Classes/RequestAwareReportInterface.php 1 addition, 1 deletiontypo3/sysext/reports/Classes/RequestAwareReportInterface.php
- typo3/sysext/reports/Classes/RequestAwareStatusProviderInterface.php 1 addition, 1 deletion...t/reports/Classes/RequestAwareStatusProviderInterface.php
Please register or sign in to comment