Trying to re-use the internal Twig template searching puts unwanted restrictions on file paths. When extending twig templates, we often have base templates in the root directory not in the Controller directory. View automatically sets the templatePath to the Controller name.
Always load twig templates relative to the root template paths.
This is the expected behavior coming from legacy TwigView as well. This was missed in unit tests because we don't build TwigView through ViewBuilder from a Controller which automatically add the config.
Trying to re-use the internal Twig template searching puts unwanted restrictions on file paths. When extending twig templates, we often have base templates in the root directory not in the Controller directory. View automatically sets the
templatePathto the Controller name.Always load twig templates relative to the root template paths.
This is the expected behavior coming from legacy TwigView as well. This was missed in unit tests because we don't build TwigView through
ViewBuilderfrom a Controller which automatically add the config.