Feature #102927
open
Integrator-oriented optimization of the DebugViewHelper
0%
Description
The current version of the DebugViewHelper sometimes causes confusion among integrators, as it does not provide all the information that can be used in Fluid.
For example, think of public getter methods without a class property such as FileReference::getProperties, usable via {yourFileRef.properties}.
The DebugViewHelper is currently only a wrapper around DebuggerUtility from EXT:extbase.
However, the result of DebuggerUtility is developer-oriented. DebugViewHelper, on the other hand, is used in Fluid and should be integrator-oriented.
A corresponding proof of concept has already been implemented by @Daniel Siepmann for TYPO3 11. It may be possible to implement a corresponding core feature on this basis.
Updated by Daniel Siepmann 3 months ago
The POC is available at: https://github.com/werkraum-media/fdebug
It is basically a copy of the debugger with adjustments. The idea was to play around and find a working way and see whether this will work out.
E.g. it needs to resolve all data in order to render. That could trigger side effects, etc.
But it worked so far in 10 and 11. I don't have an idea how this should be integrated into the Core. I guess the existing class needs a huge refactoring in order to use it in different contexts.