Provide some means to deduplicate the base template #20
Comments
|
Hi, This is the pattern I use in my own websites: markup::define! {
Layout<Content: markup::Render>(content: Content, dark_mode: bool) {
@markup::doctype()
html[lang="en", class=dark_mode.then(|| "dark_mode")] {
body {
#container {
@content
}
}
}
}
}
// Use
@Layout {
content: markup::new! {
div {}
},
dark_mode: true,
}If there are more than a couple of fields that need to be passed to the Does this help? |
|
I hadn't tried using I can't say whether it works yet since I only just finished transcribing the templates over and haven't yet tried switching the actix-web routes over to calling the markup.rs versions. EDIT: (Upon discovering that the docs for EDIT: ...and I needn't have explained that thoroughly. The rustdocs for A strange situation I find myself in when I'll probably recommend Sailfish over markdown.rs, not on performance or security considerations, but because it would reflect terribly on me to have to say "Here. The docs are in a deleted version of the README from an old commit." |
|
Sorry about the state of the docs. I'm thinking of just cleaning up the deleted parts of the README and putting it back. Also to be clear, markup::define! {
Layout<Content: markup::Render>(content: Content, dark_mode: bool) {
@markup::doctype()
html[lang="en", class=dark_mode.then(|| "dark_mode")] {
head {
title { @title }
}
body {
#container {
@content
}
}
}
}
Index(message: &'static str) {
h1 { @message }
}
}
// Use
@Layout {
content: Index { message: "hello" },
dark_mode: true,
} |
|
That looks like what I tried, and wound up throwing away after getting errors like this unless I made my templates horrendously ugly: EDIT: By horrendously ugly, I mean turning pretty much every variable access from a simple |
|
Alternative is matching, but personally I'd be using a direct iterator here: markup::define! {
List<T: markup::Render>(items: impl IntoIterator<Item = T>) {
@for item in items {
@item
}
}
}Mostly since IntoIterator is more general here, and is returned with a DoubleEndedIterator + Iterator, among others. Though I personally put sorting differently, as a list of groups which get sorted among themselves... but that's another talk. |
|
That particular example is part of an ugly rapid-protoype that I recently implemented, and will probably be turning into a match once I finish porting the templates, but other examples included turning |
I currently have to manually include something like this in every top-level template I write and it'd be really nice if I could deduplicate it.
I tries playing around with the
whereclausesand theRendertrait and making a pair ofFooandFooInner` templates, where the inner template is effectively what an AJAX response would return, but gave up as the need to manually undo the reference-taking for the arguments caused by the outer template calling the inner one made the inner template very cluttered and ugly.In a more HTML-styled template language, this'd typically be solved either by "template inheritance", which looks like this in Django/Jinja/Twig-style templates...
base.tmpl:
specific.tmpl:
...or by abusing the template language's dynamic scoping and runtime evaluation to render "specific.tmpl" by rendering "base.tmpl" and passing in a string argument which is used as the path to
include!, relying on how various template languages default to exposing the the template arguments as global variables to what youinclude!.The text was updated successfully, but these errors were encountered: