TJ
TJ
we'll have to name `include()` something different if we want dynamic partial-like things, probably just `partial()` again. The `include` support that I added is compile-time
As far as layouts go, the easiest / quickest to implement would be to support only one level, and to not go all crazy like Jade
I've never used them in Jade beyond a single layout haha, I find it kinda overkill personally but hey
it'll just take a bit longer to implement / test
it's not really that it's complex, it's just that I have 250+ other projects haha
I'm +1 for layouts and sync partials that cache. It's easy to over-complicate things as far as crazy inheritance goes etc, personally I usually favour simplicity over mega-DRY solutions
I'd still leave `include` as compile-time, but `partial(name, locals)` would be this new thing. We can just take the `filename` passed to ejs, grab the `dirname()` from that, `join(dir, name)`...
nah, I'm highly anti-extend on the client-side, I'm not convinced there's any use there, on the server it's reasonable since you're constructing large strings of markup
it may be useful to default `partial()` to merge the parent's locals (this is what express did in 2x)
yup, keys passed directly to `partial()` would of course take precedence but otherwise inherit the parent's