SymfonyWorld Online 2021 Summer Edition
June 17 – 18, 2021
SymfonyWorld Online 2021 Winter Edition
December 9 – 10, 2021
  1. Home
  2. Documentation
  3. Bundles
  4. SensioFrameworkExtraBundle
  5. @Template

@Template

6.0 version
Maintained
6.0
edit this page

@Template

Usage

The @Template annotation associates a controller with a template name:

  • Annotations
     1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
    use Sensio\Bundle\FrameworkExtraBundle\Configuration\Template;

/**
 * @Template("@SensioBlog/post/show.html.twig")
 */
public function show($id)
{
    // get the Post
    $post = ...;

    return array('post' => $post);
}
  • Attributes
     1
 2
 3
 4
 5
 6
 7
 8
 9
10
    use Sensio\Bundle\FrameworkExtraBundle\Configuration\Template;

#[Template('@SensioBlog/post/show.html.twig')]
public function show($id)
{
    // get the Post
    $post = ...;

    return array('post' => $post);
}

When using the @Template annotation, the controller should return an array of parameters to pass to the view instead of a Response object.

Note

If you want to stream your template, you can make it with the following configuration:

  • Annotations
    1
2
3
4
5
6
7
    /**
 * @Template(isStreamable=true)
 */
public function show($id)
{
    // ...
}
  • Attributes
    1
2
3
4
5
    #[Template(isStreamable: true)]
public function show($id)
{
    // ...
}

Tip

If the action returns a Response object, the @Template annotation is simply ignored.

If the template is named after the controller and action names, which is the case for the above example, you can even omit the annotation value:

  • Annotations
     1
 2
 3
 4
 5
 6
 7
 8
 9
10
    /**
 * @Template
 */
public function show($id)
{
    // get the Post
    $post = ...;

    return array('post' => $post);
}
  • Attributes
    1
2
3
4
5
6
7
8
    #[Template]
public function show($id)
{
    // get the Post
    $post = ...;

    return array('post' => $post);
}

Tip

Sub-namespaces are converted into underscores. The Sensio\BlogBundle\Controller\UserProfileController::showDetails() action will resolve to @SensioBlog/user_profile/show_details.html.twig

And if the only parameters to pass to the template are method arguments, you can use the vars attribute instead of returning an array. This is very useful in combination with the @ParamConverter annotation:

  • Annotations
    1
2
3
4
5
6
7
    /**
 * @ParamConverter("post", class="SensioBlogBundle:Post")
 * @Template("@SensioBlog/post/show.html.twig", vars={"post"})
 */
public function show(Post $post)
{
}
  • Attributes
    1
2
3
4
5
    #[ParamConverter('post', class: 'SensioBlogBundle:Post')]
#[Template('@SensioBlog/post/show.html.twig"', vars: ['post'])]
public function show(Post $post)
{
}

which, thanks to conventions, is equivalent to the following configuration:

  • Annotations
    1
2
3
4
5
6
    /**
 * @Template(vars={"post"})
 */
public function show(Post $post)
{
}
  • Attributes
    1
2
3
4
    #[Template(vars: ['post'])]
public function show(Post $post)
{
}

You can make it even more concise as all method arguments are automatically passed to the template if the method returns null and no vars attribute is defined:

  • Annotations
    1
2
3
4
5
6
    /**
 * @Template
 */
public function show(Post $post)
{
}
  • Attributes
    1
2
3
4
    #[Template]
public function show(Post $post)
{
}

This work, including the code samples, is licensed under a Creative Commons BY-SA 3.0 license.