[TASK] Inject requestId into LogRecords
Do not use global state from Bootstrap::getInstance(), rather pass the requestId from LogManager through the Logger to the LogRecord. We do not have a core object container yet, therefore Bootstrap now creates a LogManager, injects the requestId and stores that instance as singleton in the GeneralUtility singleton storage. Change-Id: Ia9af3c3a0e029a3748045fcf73e92f874f4a37ba Releases: master Resolves: #84082 Reviewed-on: https://review.typo3.org/55938 Tested-by:TYPO3com <no-reply@typo3.com> Reviewed-by:
Frank Naegler <frank.naegler@typo3.org> Tested-by:
Frank Naegler <frank.naegler@typo3.org> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch>
Showing
- typo3/sysext/core/Classes/Core/Bootstrap.php 2 additions, 11 deletionstypo3/sysext/core/Classes/Core/Bootstrap.php
- typo3/sysext/core/Classes/Log/LogManager.php 13 additions, 3 deletionstypo3/sysext/core/Classes/Log/LogManager.php
- typo3/sysext/core/Classes/Log/LogRecord.php 3 additions, 4 deletionstypo3/sysext/core/Classes/Log/LogRecord.php
- typo3/sysext/core/Classes/Log/Logger.php 11 additions, 2 deletionstypo3/sysext/core/Classes/Log/Logger.php
- typo3/sysext/core/Tests/Functional/Log/Writer/DatabaseWriterTest.php 3 additions, 3 deletions...t/core/Tests/Functional/Log/Writer/DatabaseWriterTest.php
Please register or sign in to comment