Crates.io | hypersynthetic |
lib.rs | hypersynthetic |
version | 0.7.1 |
source | src |
created_at | 2023-08-19 15:20:16.737589 |
updated_at | 2024-11-10 13:27:02.070407 |
description | An HTML template engine that chose composition over inheritance |
homepage | https://github.com/sanchopanca/hypersynthetic |
repository | https://github.com/sanchopanca/hypersynthetic |
max_upload_size | |
id | 948749 |
size | 45,140 |
Hypersynthetic is a library for writing HTML inside Rust. It is inspired by JSX and HEEx templates, and tries to be different from Tera and Minijinja by enabling Locality of Behavior (LOB) and only allowing reusing HTML code via composition and not via inheritance. It is suitable for building traditional web applications, where backend responds with HTML.
Here is an example of what hypersynthetic can do:
use hypersynthetic::prelude::*;
#[component]
fn TodoItem(text: &str, done: bool) -> HtmlFragment {
let text_decoration = if done { "line-through" } else { "none" };
html! {
<li style="text-decoration: {text_decoration};">
{text}
</li>
}
}
fn main() {
let todo_list = vec![
("Buy Milk", true),
("Read Rust Book", false),
("Write Web App using html! macro", false),
];
let html_list = html! {
<ul>
<TodoItem :for={(text, done) in todo_list} text={text} done={done} />
</ul>
};
// ... Render `html_list` into your application.
html_list.to_string();
}
In this example:
The TodoItem
component displays a to-do item, striking it through if it’s done.
The main function defines a list of to-dos and uses the :for
attribute to loop over them, rendering each one using the TodoItem
component.
See the html macro for the description of the syntax and component macro for more details about using components
The following features enable integration with popular web frameworks. See the Cargo Book to learn more about enabling features.
rocket
: Enables integration with the Rocket web framework and allows to return HtmlFragment
from handlers.
axum
: Enables integration with the Axum web framework and allows to return HtmlFragment
from handlers.
Licensed under either of
at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.