The #TYPO3#Debug#ViewHelper in #Fluid sometimes confuses #integrators. Think of public getter without class property like FileReference::getProperties usable via yourFileRef.properties. Wouldn't it be better to list ALL information that can be used? What do you think?
@ErHaWeb how about asking for a budget the next time? Or open an issue and discuss in core dev or with structured content initiative? As they also strive to lower the barrier for new users/integrators of TYPO3.
@danielsiepmann First of all, I wanted to address the issue and get your opinion on it as I occasionally come across it when giving help in online forums. It's great that you already have an implementation for this 👍 I think it's a good idea to integrate this into the core sooner or later to improve the integrators' experience with the system. I don't see myself in a position to get something like this off the ground due to lack of time, but I support the idea to the best of my ability.
@ErHaWeb I actually stopped working on it. The "project" is still not compatible with v12. And I don't know how much work it would be to properly adjust the debugger within TYPO3 to support both.
The project was more a POC. So "someone" still needs to work on it :)
@danielsiepmann Another cool TYPO3 hobby project 😄. Unfortunately I already have so many of them. Hopefully there will be someone™️ else in the community who will take care of it. Your POC is definitely a good basis. I have at least created an issue for it https://forge.typo3.org/issues/102927
Add comment