in reply to Can you include templates in Template Toolkit without specifying the file extension?

Hi,

See https://metacpan.org/pod/Template#LOAD_TEMPLATES and https://metacpan.org/pod/Template::Provider#SUBCLASSING

and make a provider, something like this untested one 

package Template::Provider::ImplicitExtension;
use parent qw/ Template::Provider /;
sub _template_modified {
   my ($self, $path) = @_;
   return $self->SUPER::_template_modified( $path.'.tt2');
}
sub _template_content {
   my ($self, $path) = @_;
   return $self->SUPER::_template_content( $path.'.tt2');
}

[download]
  • Comment on Re: Can you include templates in Template Toolkit without specifying the file extension?
  • Download Code

Replies are listed 'Best First'.
Re^2: Can you include templates in Template Toolkit without specifying the file extension?
by TrixieTang (Sexton) on May 17, 2017 at 17:59 UTC

    This is exactly what I was looking for. Thanks.

    I currently have it working, but the '.html' bit is hard coded into the provider that I made (your code worked fine without any tweaks BTW), is there some a way to pass one of my configuration variables to the provider so the template extension isn't hard coded into the provider and can be changed from a config file?

[reply]

      See the synopsis section of Template::Provider::ArchiveTar on how you can pass parameters to your own template provider.

      This will mean that you will need to instantiate your own Template Toolkit object.

[reply]
        "This will mean that you will need to instantiate your own Template Toolkit object."

        Is this good or bad? How do I avoid having to do this if bad? How do I do this if good?

[reply]

In Section Seekers of Perl Wisdom