soliciting feedback: which of these two syntaxes do you prefer?
kulupu jynbody {
@each section in $(sections) where $(:title section) {
$(:title section)
}
$content
}
body {
@each section in (sections) where (:title section) {
$(:title section)
}
$content
}
(note that $ has disappeared from the @each line in the second one)
(:title section) everywhere, even in the bodythis is hot
body {
header.site-header {
nav.site-nav {
@each section in (sections) where (predicate section) {
a.page-link[href=$section.url] { $section.title }
}
}
}
ok follow-up question: which of these do you like better?
A: all of these rules:
div { Hello world } expands to <div>Hello world</div>div { span { Hi } } expands to <div><span>Hi</span></div>div { "Hello" span { world } } expands to <div>Hello<span>world</span></div>div div > span { Hi } and p { Hello span { world } } are parse errorsB: all of these rules:
div { "Hello world" } expands to <div>Hello world</div>div { span { "Hi" } } expands to <div><span>Hi</span></div>div div > span { "Hi" } expands to <div></div><div><span>Hi</span></div>p { Hello span { world } } expands to <p><Hello></Hello><span><world></world></span></p>C: something else
Julia Evanshidden -> hidden="", but that's easy to remove.@jyn the main thing i remember is this issue I ran into with templ where it required you to quote attribute values https://github.com/a-h/templ/issues/963 (and also how templ requires that <li> and <p> tags be closed)
the "li tags must be closed" thing doesn't seem too relevant in this case though I am curious about how br and hr tags would be represented
hr; and empty blocks require a trailing div {}, so bare names are an error now unless they're followed by a > child selector.