pub struct Tera { /* private fields */ }
Expand description
Main point of interaction in this library.
The Tera
struct is the primary interface for working with the Tera template engine. It contains parsed templates, registered filters (which can filter
data), functions, and testers. It also contains some configuration options, such as a list of
suffixes for files that have autoescaping turned on.
It is responsible for:
- Loading and managing templates from files or strings
- Parsing templates and checking for syntax errors
- Maintaining a cache of compiled templates for efficient rendering
- Providing an interface for rendering templates with given contexts
- Managing template inheritance and includes
- Handling custom filters and functions
- Overriding settings, such as autoescape rules
§Example
Basic usage:
use tera::Tera;
// Create a new Tera instance and add a template from a string
let mut tera = Tera::new("templates/**/*").unwrap();
tera.add_raw_template("hello", "Hello, {{ name }}!").unwrap();
// Prepare the context with some data
let mut context = tera::Context::new();
context.insert("name", "World");
// Render the template with the given context
let rendered = tera.render("hello", &context).unwrap();
assert_eq!(rendered, "Hello, World!");
Implementations§
Source§impl Tera
impl Tera
Sourcepub fn new(dir: &str) -> Result<Tera, Error>
pub fn new(dir: &str) -> Result<Tera, Error>
Create a new instance of Tera, containing all the parsed templates found in the dir
glob.
A glob is a pattern for matching multiple file paths, employing special characters such as
the single asterisk (*
) to match any sequence of characters within a single directory
level, and the double asterisk (**
) to match any sequence of characters across multiple
directory levels, thereby providing a flexible and concise way to select files based on
their names, extensions, or hierarchical relationships. For example, the glob pattern
templates/*.html
will match all files with the .html
extension located directly inside
the templates
folder, while the glob pattern templates/**/*.html
will match all files
with the .html
extension directly inside or in a subdirectory of templates
.
In order to create an empty Tera
instance, you can use the Default
implementation.
§Examples
Basic usage:
let tera = Tera::new("examples/basic/templates/**/*").unwrap();
Sourcepub fn parse(dir: &str) -> Result<Tera, Error>
pub fn parse(dir: &str) -> Result<Tera, Error>
Create a new instance of Tera, containing all the parsed templates found in the dir
glob.
The difference to Tera::new
is that it won’t build the inheritance chains
automatically, so you are free to modify the templates if you need to.
§Inheritance Chains
You will not get a working Tera instance using this method. You will need to call
build_inheritance_chains()
to make it usable.
§Examples
Basic usage:
let mut tera = Tera::parse("examples/basic/templates/**/*").unwrap();
// do not forget to build the inheritance chains
tera.build_inheritance_chains().unwrap();
Sourcepub fn build_inheritance_chains(&mut self) -> Result<(), Error>
pub fn build_inheritance_chains(&mut self) -> Result<(), Error>
Build inheritance chains for loaded templates.
We need to know the hierarchy of templates to be able to render multiple extends level. This happens at compile-time to avoid checking it every time we want to render a template. This also checks for soundness issues in the inheritance chains, such as missing template or circular extends. It also builds the block inheritance chain and detects when super() is called in a place where it can’t possibly work
You generally don’t need to call that yourself, unless you used Tera::parse()
.
Sourcepub fn check_macro_files(&self) -> Result<(), Error>
pub fn check_macro_files(&self) -> Result<(), Error>
We keep track of macro files loaded in each Template so we can know whether one or them is missing and error accordingly before the user tries to render a template.
As with build_inheritance_chains()
, you don’t usually need to call that yourself.
Sourcepub fn render(
&self,
template_name: &str,
context: &Context,
) -> Result<String, Error>
pub fn render( &self, template_name: &str, context: &Context, ) -> Result<String, Error>
Renders a Tera template given a Context
.
§Examples
Basic usage:
// Create new tera instance with sample template
let mut tera = Tera::default();
tera.add_raw_template("info", "My age is {{ age }}.");
// Create new context
let mut context = Context::new();
context.insert("age", &18);
// Render template using the context
let output = tera.render("info", &context).unwrap();
assert_eq!(output, "My age is 18.");
To render a template with an empty context, simply pass an empty Context
object.
// Create new tera instance with demo template
let mut tera = Tera::default();
tera.add_raw_template("hello.html", "<h1>Hello</h1>");
// Render a template with an empty context
let output = tera.render("hello.html", &Context::new()).unwrap();
assert_eq!(output, "<h1>Hello</h1>");
Sourcepub fn render_to(
&self,
template_name: &str,
context: &Context,
write: impl Write,
) -> Result<(), Error>
pub fn render_to( &self, template_name: &str, context: &Context, write: impl Write, ) -> Result<(), Error>
Renders a Tera template given a Context
to something that implements Write
.
The only difference from render()
is that this version doesn’t convert
buffer to a String, allowing to render directly to anything that implements Write
. For
example, this could be used to write directly to a File
.
Any I/O error will be reported in the result.
§Examples
Rendering into a Vec<u8>
:
let mut tera = Tera::default();
tera.add_raw_template("index.html", "<p>{{ name }}</p>");
// Rendering a template to an internal buffer
let mut buffer = Vec::new();
let mut context = Context::new();
context.insert("name", "John Wick");
tera.render_to("index.html", &context, &mut buffer).unwrap();
assert_eq!(buffer, b"<p>John Wick</p>");
Sourcepub fn render_str(
&mut self,
input: &str,
context: &Context,
) -> Result<String, Error>
pub fn render_str( &mut self, input: &str, context: &Context, ) -> Result<String, Error>
Renders a one off template (for example a template coming from a user
input) given a Context
and an instance of Tera. This allows you to
render templates using custom filters or functions.
Any errors will mention the __tera_one_off
template: this is the name
given to the template by Tera.
let mut context = Context::new();
context.insert("greeting", &"Hello");
let string = tera.render_str("{{ greeting }} World!", &context)?;
assert_eq!(string, "Hello World!");
Sourcepub fn one_off(
input: &str,
context: &Context,
autoescape: bool,
) -> Result<String, Error>
pub fn one_off( input: &str, context: &Context, autoescape: bool, ) -> Result<String, Error>
Renders a one off template (for example a template coming from a user input) given a Context
This creates a separate instance of Tera with no possibilities of adding custom filters
or testers, parses the template and render it immediately.
Any errors will mention the __tera_one_off
template: this is the name given to the template by
Tera
let mut context = Context::new();
context.insert("greeting", &"hello");
Tera::one_off("{{ greeting }} world", &context, true);
Sourcepub fn get_template_names(&self) -> impl Iterator<Item = &str>
pub fn get_template_names(&self) -> impl Iterator<Item = &str>
Returns an iterator over the names of all registered templates in an unspecified order.
§Example
use tera::Tera;
let mut tera = Tera::default();
tera.add_raw_template("foo", "{{ hello }}");
tera.add_raw_template("another-one.html", "contents go here");
let names: Vec<_> = tera.get_template_names().collect();
assert_eq!(names.len(), 2);
assert!(names.contains(&"foo"));
assert!(names.contains(&"another-one.html"));
Sourcepub fn add_raw_template(
&mut self,
name: &str,
content: &str,
) -> Result<(), Error>
pub fn add_raw_template( &mut self, name: &str, content: &str, ) -> Result<(), Error>
Add a single template to the Tera instance.
This will error if the inheritance chain can’t be built, such as adding a child template without the parent one.
§Bulk loading
If you want to add several templates, use
add_raw_templates()
.
§Examples
Basic usage:
let mut tera = Tera::default();
tera.add_raw_template("new.html", "Blabla").unwrap();
Sourcepub fn add_raw_templates<I, N, C>(&mut self, templates: I) -> Result<(), Error>
pub fn add_raw_templates<I, N, C>(&mut self, templates: I) -> Result<(), Error>
Add all the templates given to the Tera instance
This will error if the inheritance chain can’t be built, such as adding a child template without the parent one.
tera.add_raw_templates(vec![
("new.html", "blabla"),
("new2.html", "hello"),
]);
Sourcepub fn add_template_file<P>(
&mut self,
path: P,
name: Option<&str>,
) -> Result<(), Error>
pub fn add_template_file<P>( &mut self, path: P, name: Option<&str>, ) -> Result<(), Error>
Add a single template from a path to the Tera instance. The default name for the template is
the path given, but this can be renamed with the name
parameter
This will error if the inheritance chain can’t be built, such as adding a child template without the parent one. If you want to add several file, use Tera::add_template_files
let mut tera = Tera::default();
// Rename template with custom name
tera.add_template_file("examples/basic/templates/macros.html", Some("macros.html")).unwrap();
// Use path as name
tera.add_template_file("examples/basic/templates/base.html", None).unwrap();
Sourcepub fn add_template_files<I, P, N>(&mut self, files: I) -> Result<(), Error>
pub fn add_template_files<I, P, N>(&mut self, files: I) -> Result<(), Error>
Add several templates from paths to the Tera instance.
The default name for the template is the path given, but this can be renamed with the second parameter of the tuple
This will error if the inheritance chain can’t be built, such as adding a child template without the parent one.
let mut tera = Tera::default();
tera.add_template_files(vec![
("./path/to/template.tera", None), // this template will have the value of path1 as name
("./path/to/other.tera", Some("hey")), // this template will have `hey` as name
]);
Sourcepub fn register_filter<F>(&mut self, name: &str, filter: F)where
F: Filter + 'static,
pub fn register_filter<F>(&mut self, name: &str, filter: F)where
F: Filter + 'static,
Register a filter with Tera.
If a filter with that name already exists, it will be overwritten
tera.register_filter("upper", string::upper);
Sourcepub fn register_tester<T>(&mut self, name: &str, tester: T)where
T: Test + 'static,
pub fn register_tester<T>(&mut self, name: &str, tester: T)where
T: Test + 'static,
Register a tester with Tera.
If a tester with that name already exists, it will be overwritten
tera.register_tester("odd", testers::odd);
Sourcepub fn register_function<F>(&mut self, name: &str, function: F)where
F: Function + 'static,
pub fn register_function<F>(&mut self, name: &str, function: F)where
F: Function + 'static,
Register a function with Tera.
This registers an arbitrary function to make it callable from within a template. If a function with that name already exists, it will be overwritten.
tera.register_function("range", range);
Sourcepub fn autoescape_on(&mut self, suffixes: Vec<&'static str>)
pub fn autoescape_on(&mut self, suffixes: Vec<&'static str>)
Select which suffix(es) to automatically do HTML escaping on.
By default, autoescaping is performed on .html
, .htm
and .xml
template files. Only
call this function if you wish to change the defaults.
§Examples
Basic usage:
let mut tera = Tera::default();
// escape only files ending with `.php.html`
tera.autoescape_on(vec![".php.html"]);
// disable autoescaping completely
tera.autoescape_on(vec![]);
Sourcepub fn set_escape_fn(&mut self, function: fn(_: &str) -> String)
pub fn set_escape_fn(&mut self, function: fn(_: &str) -> String)
Set user-defined function that is used to escape content.
Often times, arbitrary data needs to be injected into a template without allowing injection attacks. For this reason, typically escaping is performed on all input. By default, the escaping function will produce HTML escapes, but it can be overridden to produce escapes more appropriate to the language being used.
Inside templates, escaping can be turned off for specific content using the safe
filter.
For example, the string {{ data }}
inside a template will escape data, while {{ data | safe }}
will not.
§Examples
Basic usage:
// Create new Tera instance
let mut tera = Tera::default();
// Override escape function
tera.set_escape_fn(|input| {
input.escape_default().collect()
});
// Create template and enable autoescape
tera.add_raw_template("hello.js", "const data = \"{{ content }}\";").unwrap();
tera.autoescape_on(vec!["js"]);
// Create context with some data
let mut context = Context::new();
context.insert("content", &"Hello\n\'world\"!");
// Render template
let result = tera.render("hello.js", &context).unwrap();
assert_eq!(result, r#"const data = "Hello\n\'world\"!";"#);
Sourcepub fn reset_escape_fn(&mut self)
pub fn reset_escape_fn(&mut self)
Reset escape function to default escape_html()
.
Sourcepub fn full_reload(&mut self) -> Result<(), Error>
pub fn full_reload(&mut self) -> Result<(), Error>
Re-parse all templates found in the glob given to Tera.
Use this when you are watching a directory and want to reload everything, for example when a file is added.
If you are adding templates without using a glob, we can’t know when a template is deleted, which would result in an error if we are trying to reload that file.
Sourcepub fn extend(&mut self, other: &Tera) -> Result<(), Error>
pub fn extend(&mut self, other: &Tera) -> Result<(), Error>
Extend this Tera
instance with the templates, filters, testers and functions defined in
another instance.
Use that method when you want to add a given Tera instance templates/filters/testers/functions to your own. If a template/filter/tester/function with the same name already exists in your instance, it will not be overwritten.
// add all the templates from FRAMEWORK_TERA
// except the ones that have an identical name to the ones in `my_tera`
my_tera.extend(&FRAMEWORK_TERA);
Trait Implementations§
Auto Trait Implementations§
impl Freeze for Tera
impl !RefUnwindSafe for Tera
impl Send for Tera
impl Sync for Tera
impl Unpin for Tera
impl !UnwindSafe for Tera
Blanket Implementations§
Source§impl<T> AsAny for Twhere
T: Any,
impl<T> AsAny for Twhere
T: Any,
fn as_any_ref(&self) -> &(dyn Any + 'static)
fn as_any_mut(&mut self) -> &mut (dyn Any + 'static)
Source§impl<'a, T, E> AsTaggedExplicit<'a, E> for Twhere
T: 'a,
impl<'a, T, E> AsTaggedExplicit<'a, E> for Twhere
T: 'a,
Source§impl<'a, T, E> AsTaggedImplicit<'a, E> for Twhere
T: 'a,
impl<'a, T, E> AsTaggedImplicit<'a, E> for Twhere
T: 'a,
Source§impl<T> BorrowMut<T> for Twhere
T: ?Sized,
impl<T> BorrowMut<T> for Twhere
T: ?Sized,
Source§fn borrow_mut(&mut self) -> &mut T
fn borrow_mut(&mut self) -> &mut T
Source§impl<T> CloneToUninit for Twhere
T: Clone,
impl<T> CloneToUninit for Twhere
T: Clone,
Source§impl<T> Instrument for T
impl<T> Instrument for T
Source§fn instrument(self, span: Span) -> Instrumented<Self>
fn instrument(self, span: Span) -> Instrumented<Self>
Source§fn in_current_span(self) -> Instrumented<Self>
fn in_current_span(self) -> Instrumented<Self>
Source§impl<T> IntoEither for T
impl<T> IntoEither for T
Source§fn into_either(self, into_left: bool) -> Either<Self, Self>
fn into_either(self, into_left: bool) -> Either<Self, Self>
self
into a Left
variant of Either<Self, Self>
if into_left
is true
.
Converts self
into a Right
variant of Either<Self, Self>
otherwise. Read moreSource§fn into_either_with<F>(self, into_left: F) -> Either<Self, Self>
fn into_either_with<F>(self, into_left: F) -> Either<Self, Self>
self
into a Left
variant of Either<Self, Self>
if into_left(&self)
returns true
.
Converts self
into a Right
variant of Either<Self, Self>
otherwise. Read moreSource§impl<T> Paint for Twhere
T: ?Sized,
impl<T> Paint for Twhere
T: ?Sized,
Source§fn fg(&self, value: Color) -> Painted<&T>
fn fg(&self, value: Color) -> Painted<&T>
Returns a styled value derived from self
with the foreground set to
value
.
This method should be used rarely. Instead, prefer to use color-specific
builder methods like red()
and
green()
, which have the same functionality but are
pithier.
§Example
Set foreground color to white using fg()
:
use yansi::{Paint, Color};
painted.fg(Color::White);
Set foreground color to white using white()
.
use yansi::Paint;
painted.white();
Source§fn bright_black(&self) -> Painted<&T>
fn bright_black(&self) -> Painted<&T>
Returns self
with the
fg()
set to
Color::BrightBlack
.
§Example
println!("{}", value.bright_black());
Source§fn bright_red(&self) -> Painted<&T>
fn bright_red(&self) -> Painted<&T>
Source§fn bright_green(&self) -> Painted<&T>
fn bright_green(&self) -> Painted<&T>
Returns self
with the
fg()
set to
Color::BrightGreen
.
§Example
println!("{}", value.bright_green());
Source§fn bright_yellow(&self) -> Painted<&T>
fn bright_yellow(&self) -> Painted<&T>
Returns self
with the
fg()
set to
Color::BrightYellow
.
§Example
println!("{}", value.bright_yellow());
Source§fn bright_blue(&self) -> Painted<&T>
fn bright_blue(&self) -> Painted<&T>
Source§fn bright_magenta(&self) -> Painted<&T>
fn bright_magenta(&self) -> Painted<&T>
Returns self
with the
fg()
set to
Color::BrightMagenta
.
§Example
println!("{}", value.bright_magenta());
Source§fn bright_cyan(&self) -> Painted<&T>
fn bright_cyan(&self) -> Painted<&T>
Source§fn bright_white(&self) -> Painted<&T>
fn bright_white(&self) -> Painted<&T>
Returns self
with the
fg()
set to
Color::BrightWhite
.
§Example
println!("{}", value.bright_white());
Source§fn bg(&self, value: Color) -> Painted<&T>
fn bg(&self, value: Color) -> Painted<&T>
Returns a styled value derived from self
with the background set to
value
.
This method should be used rarely. Instead, prefer to use color-specific
builder methods like on_red()
and
on_green()
, which have the same functionality but
are pithier.
§Example
Set background color to red using fg()
:
use yansi::{Paint, Color};
painted.bg(Color::Red);
Set background color to red using on_red()
.
use yansi::Paint;
painted.on_red();
Source§fn on_primary(&self) -> Painted<&T>
fn on_primary(&self) -> Painted<&T>
Source§fn on_magenta(&self) -> Painted<&T>
fn on_magenta(&self) -> Painted<&T>
Source§fn on_bright_black(&self) -> Painted<&T>
fn on_bright_black(&self) -> Painted<&T>
Returns self
with the
bg()
set to
Color::BrightBlack
.
§Example
println!("{}", value.on_bright_black());
Source§fn on_bright_red(&self) -> Painted<&T>
fn on_bright_red(&self) -> Painted<&T>
Source§fn on_bright_green(&self) -> Painted<&T>
fn on_bright_green(&self) -> Painted<&T>
Returns self
with the
bg()
set to
Color::BrightGreen
.
§Example
println!("{}", value.on_bright_green());
Source§fn on_bright_yellow(&self) -> Painted<&T>
fn on_bright_yellow(&self) -> Painted<&T>
Returns self
with the
bg()
set to
Color::BrightYellow
.
§Example
println!("{}", value.on_bright_yellow());
Source§fn on_bright_blue(&self) -> Painted<&T>
fn on_bright_blue(&self) -> Painted<&T>
Returns self
with the
bg()
set to
Color::BrightBlue
.
§Example
println!("{}", value.on_bright_blue());
Source§fn on_bright_magenta(&self) -> Painted<&T>
fn on_bright_magenta(&self) -> Painted<&T>
Returns self
with the
bg()
set to
Color::BrightMagenta
.
§Example
println!("{}", value.on_bright_magenta());
Source§fn on_bright_cyan(&self) -> Painted<&T>
fn on_bright_cyan(&self) -> Painted<&T>
Returns self
with the
bg()
set to
Color::BrightCyan
.
§Example
println!("{}", value.on_bright_cyan());
Source§fn on_bright_white(&self) -> Painted<&T>
fn on_bright_white(&self) -> Painted<&T>
Returns self
with the
bg()
set to
Color::BrightWhite
.
§Example
println!("{}", value.on_bright_white());
Source§fn attr(&self, value: Attribute) -> Painted<&T>
fn attr(&self, value: Attribute) -> Painted<&T>
Enables the styling Attribute
value
.
This method should be used rarely. Instead, prefer to use
attribute-specific builder methods like bold()
and
underline()
, which have the same functionality
but are pithier.
§Example
Make text bold using attr()
:
use yansi::{Paint, Attribute};
painted.attr(Attribute::Bold);
Make text bold using using bold()
.
use yansi::Paint;
painted.bold();
Source§fn underline(&self) -> Painted<&T>
fn underline(&self) -> Painted<&T>
Returns self
with the
attr()
set to
Attribute::Underline
.
§Example
println!("{}", value.underline());
Source§fn rapid_blink(&self) -> Painted<&T>
fn rapid_blink(&self) -> Painted<&T>
Returns self
with the
attr()
set to
Attribute::RapidBlink
.
§Example
println!("{}", value.rapid_blink());
Source§fn quirk(&self, value: Quirk) -> Painted<&T>
fn quirk(&self, value: Quirk) -> Painted<&T>
Enables the yansi
Quirk
value
.
This method should be used rarely. Instead, prefer to use quirk-specific
builder methods like mask()
and
wrap()
, which have the same functionality but are
pithier.
§Example
Enable wrapping using .quirk()
:
use yansi::{Paint, Quirk};
painted.quirk(Quirk::Wrap);
Enable wrapping using wrap()
.
use yansi::Paint;
painted.wrap();
Source§fn clear(&self) -> Painted<&T>
👎Deprecated since 1.0.1: renamed to resetting()
due to conflicts with Vec::clear()
.
The clear()
method will be removed in a future release.
fn clear(&self) -> Painted<&T>
resetting()
due to conflicts with Vec::clear()
.
The clear()
method will be removed in a future release.Source§fn whenever(&self, value: Condition) -> Painted<&T>
fn whenever(&self, value: Condition) -> Painted<&T>
Conditionally enable styling based on whether the Condition
value
applies. Replaces any previous condition.
See the crate level docs for more details.
§Example
Enable styling painted
only when both stdout
and stderr
are TTYs:
use yansi::{Paint, Condition};
painted.red().on_yellow().whenever(Condition::STDOUTERR_ARE_TTY);