Catalyst-View-Xslate
view release on metacpan or search on metacpan
# NAME
Catalyst::View::Xslate - Text::Xslate View Class
# SYNOPSIS
package MyApp::View::Xslate;
use Moose;
extends 'Catalyst::View::Xslate';
1;
# VIEW CONFIGURATION
You may specify the following configuration items in from your config file
or directly on the view object.
## catalyst\_var
The name used to refer to the Catalyst app object in the template
## template\_extension
The suffix used to auto generate the template name from the action name
(when you do not explicitly specify the template filename);
Do not confuse this with the `suffix` option, which is passed directly to
the Text::Xslate object instance. This option works on the filename used
for the initial request, while `suffix` controls what `cascade` and
`include` directives do inside Text::Xslate.
## content\_charset
The charset used to output the response body. The value defaults to 'UTF-8'.
## encode\_body
By default, output will be encoded to `content_charset`.
You can set it to 0 to disable this behavior.
(you need to do this if you're using `Catalyst::Plugin::Unicode::Encoding`)
__NOTE__ Starting with [Catalyst](https://metacpan.org/pod/Catalyst) version 5.90080 Catalyst will automatically
encode to UTF8 any text like body responses. You should either turn off the
body encoding step in this view using this attribute OR disable this feature
in the application (your subclass of Catalyst.pm).
MyApp->config(encoding => undef);
Failure to do so will result in double encoding.
## Text::Xslate CONFIGURATION
The following parameters are passed to the Text::Xslate constructor.
When reset during the life cyle of the Catalyst app, these parameters will
cause the previously created underlying Text::Xslate object to be cleared
## path
## cache\_dir
## cache
## header
## escape
## type
## footer
## function
## input\_layer
## module
## syntax
## verbose
## line\_start
## tag\_start
## tag\_end
## warn\_handler
## die\_handler
( run in 2.464 seconds using v1.01-cache-2.11-cpan-5837b0d9d2c )