Forbes Lindesay

I suspect I'm not alone in thinking it's an absolute killer feature. Are you OK with supporting it? We could ask somewhere to try and get a feel for how...

I don't think it'll add much to the complexity tbh. I've implemented it for QEJS and that went fine. The only difference here is that we're doing it at compile...

Cool, well I'm happy to make this fairly high on my list of priorities, so if we agree on what needs doing, I'll have something for a fortnight after it's...

Shall we make the file Loader sync then? ``` javascript var path = require('path'); var fs = require('fs'); /** * Load the contents of a file * * @param {string}...

Would keep things really nice and simple

If we go the sync and cache route, should we make them fully dynamic, removing the restriction that they must be string literals?

Yeh, sounds good, do you want to do as proposed and make the functionality pluggable? The main use case I see for doing so would be as a client side...

Fair enough, we'll just use the file system

New Proposal: # Syntax ``` ``` `extends` must be passed a string literal, `partial` works just like any other function. # Functionality ## Path resolution Paths are resolved relative to...

So are you suggesting that: File 1 ``` ``` File 2 ``` ``` ``` javascript render('file1.ejs', {foo: 'foo'}); ``` would render `foobar` That would seem fine to me if that...