New in Symfony 4.3: Deprecated the Templating component integration
Warning: This post is about an unsupported Symfony version. Some of this information may be out of date. Read the most recent Symfony Docs.
The Symfony Templating component provides the tools needed to build any kind of template system, including the loading of template files from multiple sources, monitoring them for changes and using multiple engines to render them.
In Symfony applications this component allowed using both PHP and Twig to create the templates. However, nearly all developers use Twig to create traditional templates or use the serializer to output data. That's why in Symfony 4.3 we've decided to deprecate the integration of the Templating component in Symfony applications.
This means that, starting from Symfony 5.0, we will remove support for using PHP
templates and PHP form themes. You'll need to use Twig for those templates. In
addition to deprecating several classes, services and service tags, the
hinclude_default_template configuration option has been moved to the
1 2 3 4 5 6
# config/packages/framework.yaml framework: # ... - templating: + fragments: hinclude_default_template: hinclude.html.twig
Although the number of people using PHP templates in Symfony applications is minimal compared to Twig, if enough people would volunteer to work on an alternative solution, we'd consider the creation of a new PHPTemplateBundle that provides all the deprecated classes and support files. If you are willing to help, create an issue in the main Symfony GitHub repository to kick off the discussion around this.
Comments are closed.
To ensure that comments stay relevant, they are closed for old posts.