Handlebars templating language implemented in Rust and for Rust.
If you are not familiar with handlebars language syntax, it is recommended to walk through their introduction first.
Examples are provided in source tree to demo usage of various api.
- quick the very basic example of registry and render apis
- render how to define custom helpers with function, trait impl or macro, and also how to use custom helpers.
- render_file similar to render, but render to file instead of string
demos usage of
handlebars_helper!to simplify helper development
- partials template inheritance with handlebars
- decorator how to use decorator to change data or define custom helper
- error simple case for error
a web server hosts handlebars in
dev_mode, you can edit the template and see the change without restarting your server.
Minimum Rust Version Policy
Handlebars will track Rust nightly and stable channel. When dropping support for previous stable versions, I will bump patch version and clarify in CHANGELOG.
Changelog is available in the source tree named as
Any contribution to this library is welcomed. To get started into development, I have several Help Wanted issues, with the difficulty level labeled. When running into any problem, feel free to contact me on github.
I'm always looking for maintainers to work together on this library, let me know (via email or anywhere in the issue tracker) if you want to join.
Why (this) Handlebars?
Handlebars is a real-world templating system that you can use to build your application without pain.
Isolation of Rust and HTML
This library doesn't attempt to use some macro magic to allow you to write your template within your rust code. I admit that it's fun to do that but it doesn't fit real-world use cases.
Limited but essential control structures built-in
Only essential control directives
each are built-in. This
prevents you from putting too much application logic into your template.
Extensible helper system
You can write your own helper with Rust! It can be a block helper or inline helper. Put your logic into the helper and don't repeat yourself.
A helper can be as a simple as a Rust function like:
/// register the helper
And using it in your template:
By default, handlebars-rust ships additional helpers
(compared with original js version)
that is useful when working with
script_helper feature flag enabled, you can also create helpers
for handlebars-js. This feature was in early stage. Its API was limited at the
moment, and can change in future.
Every time I look into a templating system, I will investigate its support for template inheritance.
Template include is not sufficient for template reuse. In most cases you will need a skeleton of page as parent (header, footer, etc.), and embed your page into this parent.
You can find a real example of template inheritance in
examples/partials.rs and templates used by this file.
Auto-reload in dev mode
By turning on
dev_mode, handlebars auto reloads any template and scripts that
loaded from files or directory. This can be handy for template development.
Handlebars 3.0 can be used in WebAssembly projects.
With rhai script support, you can implement your own helper with the scripting language. Together with the template lanaguage itself, template development can be fully scriptable without changing rust code.
- Iron: handlebars-iron
- Rocket: rocket/contrib
- Warp: handlebars example
- Tower-web: Built-in
- Actix: handlebars example
- Tide: tide-handlebars
- Axum: axum-template
The adopters page lists projects that uses handlebars for part of their functionalities.
The extensions page has libraries that provide additional helpers, decorators and outputs to handlebars-rust, and you can use in your own projects.
This library (handlebars-rust) is open sourced under the MIT License.