David, thank you very much for the great Tracy panel for Latte, which shows the available variables in the template. Frontend developers can then easily remove their own {dump} macro.
However, when dumping variables, I very often encounter the problem that the frontend developer does not always know what the getters are available.
For example, if a template accepts an Article variable with an App\Entity\Article entity, there is a getter for each property (for example, there is a getTitle() for the $title property), but there may be other getters that the frontend developer may not find because they do not understand PHP code and find.
I try to remove SmartObject from entities and force the use of getters, because they are safer in type and there is no magical behavior.
Thanks a lot.
David, thank you very much for the great Tracy panel for Latte, which shows the available variables in the template. Frontend developers can then easily remove their own
{dump}macro.However, when dumping variables, I very often encounter the problem that the frontend developer does not always know what the getters are available.
For example, if a template accepts an
Articlevariable with anApp\Entity\Articleentity, there is a getter for each property (for example, there is agetTitle()for the$titleproperty), but there may be other getters that the frontend developer may not find because they do not understand PHP code and find.I try to remove SmartObject from entities and force the use of getters, because they are safer in type and there is no magical behavior.
Thanks a lot.