view release on metacpan or  search on metacpan

README  view on Meta::CPAN

    "base", and "name" variables are omitted.

    $template can be anything that Template::process understands how to
    process, including the name of a template file or a reference to a test
    string. See Template::process for a full list of supported formats.

    To use the render method outside of your Catalyst app, just pass a undef
    context. This can be useful for tests, for instance.

    It is possible to forward to the render method of a TT view from inside
    Catalyst to render page fragments like this:

        my $fragment = $c->forward("View::Web", "render", $template_name, $c->stash->{fragment_data});

   Backwards compatibility note
    The render method used to just return the Template::Exception object,
    rather than just throwing it. This is now deprecated and instead the
    render method will throw an exception for new applications.

    This behaviour can be activated (and is activated in the default
    skeleton configuration) by using "render_die => 1". If you rely on the
    legacy behaviour then a warning will be issued.

lib/Catalyst/View/TT.pm  view on Meta::CPAN

C<name> variables are omitted.

C<$template> can be anything that Template::process understands how to
process, including the name of a template file or a reference to a test string.
See L<Template::process|Template/process> for a full list of supported formats.

To use the render method outside of your Catalyst app, just pass a undef context.
This can be useful for tests, for instance.

It is possible to forward to the render method of a TT view from inside Catalyst
to render page fragments like this:

    my $fragment = $c->forward("View::Web", "render", $template_name, $c->stash->{fragment_data});

=head3 Backwards compatibility note

The render method used to just return the Template::Exception object, rather
than just throwing it. This is now deprecated and instead the render method
will throw an exception for new applications.

This behaviour can be activated (and is activated in the default skeleton
configuration) by using C<< render_die => 1 >>. If you rely on the legacy
behaviour then a warning will be issued.