Used to specify the default template that should be used for a footer. It can be specified as anything that the Template::TT3::Templates template() method will accept, e.g. a template name, text references, subroutine reference, etc.

template is the default option for the service. Thus the following:

my $footer = Template::TT3::Services->service(
    footer => 'site/footer.tt3',
);

is syntactic sugar for:

my $footer = Template::TT3::Services->service(
    footer => {
        template => 'site/footer.tt3',
    },
);

This can be used to change the name of the service component. The default name is footer. If a footer is specified in the environment passed to the pipeline service function then it will be used in preference to the default template .

$pipeline->(
    context => $context,
    input   => 'example.tt3',
    footer  => 'my/footer.tt3',     # over-ride default footer template
);

If you want to have several different footer services in the same pipeline then you should give them unique names. For example, you might set one to site_footer and the other to section_footer. This allows you to change the name of either independently.

$pipeline->(
    context        => $context,
    input          => 'example.tt3',
    site_footer    => 'site/footer.tt3',
    section_footer => 'section/products/footer.tt3',
);

This is the main service method. It is called automatically when the service is bound in a pipeline that is executed. A copy of the environment is passed as the first argument (a reference to a hash array). A reference to a subroutine representing the rest of the pipeline is passed as the second argument.

The method looks in the environment for an item named footer, or whatever alternate name the service has been given (e.g. site_footer, section_footer, etc). If the item isn't specified then it instead uses the default footer template defined when the service is created. If that is undefined or set to a false value (e.g. 0 or the empty string '') then no footer is added.

Otherwise it executes the $pipeline function to render the rest of the service pipeline and then processes the footer template. It returns the output returned from $pipeline function concatenated with that generated by the footer template. If no footer is specified then it returns only the output from the $pipeline function.