Improving Fluid Developer Experience with TYPO3 v14
Simon Praetorius gives us an update on his Community Budget idea for improving the Fluid developer experience — and the first results are already landing in Fluid 5.2.
TYPO3 v14 ships with Fluid 5, the next major version of our templating engine. Alongside ongoing refactoring and modernization efforts, the Fluid team is also focusing on a topic that directly affects day-to-day work for integrators and frontend developers: developer experience (DX).
With the recent release of Fluid 5.2, several improvements have been introduced that make working with Fluid templates easier and more productive.
Autocomplete for Components
TYPO3 v14 will ship with IDE autocompletion for Fluid components out of the box.
TYPO3 v13 already supports IDE autocompletion for ViewHelpers through XML Schema Definition (XSD) files. These schemas describe the available ViewHelpers and their arguments, allowing IDEs such as PhpStorm to provide context-aware suggestions while editing templates.
The existing CLI command fluid:schema:generate has now been extended to also generate XSD files for Fluid components. These schema files are written to the var/transient directory and automatically picked up by compatible IDEs.
As a result, developers now get project-specific autocompletion for both ViewHelpers and components, improving productivity and reducing errors when working with Fluid templates.
This feature has been made possible through the current round of TYPO3 Community Budget Ideas.
Improved Exception Messages
Another long-standing issue with Fluid has been unhelpful error messages. In some cases, it was difficult to identify which template caused an exception because the template path was missing from the error output.
With Fluid 5.2 and supporting changes in the TYPO3 Core, this situation has been significantly improved. Most Fluid-related exceptions now include the full path to the affected template file, making it much easier to locate and fix problems.
In addition, the wording of several exception messages has been refined and additional context information can now be provided. Together, these changes make debugging Fluid templates far more straightforward.
Only the First Steps
While these improvements already provide a noticeable productivity boost, they are only the beginning.
With work still ongoing under this Community Budget Idea, the next steps will focus on improving editor tooling for Fluid templates. This includes work towards an official Fluid extension for Visual Studio Code and other VSCode-based editors, as well as research into a potential Fluid language server.
Both efforts aim to provide modern development tooling and make it easier for frontend developers to work with TYPO3 and Fluid.
Stay tuned for more updates in the coming weeks as this work progresses.
