require('file.vash') from within a template?

[kirbysayshi]

How hard do you think it would be to add support for:

@* list.vash *@
@{ var item = require('./list-item.vash'); }
<ul>@model.forEach(item)</ul>

Otherwise, are you constructing templates from the inside out and then passing them in, fully rendered?

I tried the above snippet, but since it's a physical temp file on disk it doesn't resolve:

Error: module "./list-item.vash" not found from "   /algoview/node_modules/vashify/.temp/0_list.vash.js"
    at notFound (   /algoview/node_modules/browserify/index.js:790:15)
    at  /algoview/node_modules/browserify/index.js:741:23
    at  /algoview/node_modules/browserify/node_modules/browser-resolve/index.js:185:24
    at  /algoview/node_modules/browserify/node_modules/resolve/lib/async.js:36:22
    at load (   /algoview/node_modules/browserify/node_modules/resolve/lib/async.js:54:43)
    at  /algoview/node_modules/browserify/node_modules/resolve/lib/async.js:60:22
    at  /algoview/node_modules/browserify/node_modules/resolve/lib/async.js:16:47
    at Object.oncomplete (fs.js:107:15)

[chevett]

oh interesting! Once I find the require statement then it is easy. However, I'm not sure how I'd go about getting all the code blocks from a vash file. Does vash have something I can use to examine the code blocks from a template?

[kirbysayshi]

Not easily, since vash's ast is very generic (mostly code vs markup). What
might be easier is if you pass the compiled file to browserify, since that
will of course be valid javascript. Is that possible?

~ Drew

On May 9, 2014, at 8:17 AM, Mike Chevett notifications@github.com wrote:

oh interesting! Once I find the require statement then it is easy. However,
I'm sure how I'd go about getting all the code blocks from a vash file.
Does vash have something I can use to examine the code blocks from a
template?

—
Reply to this email directly or view it on
GitHubhttps://github.com//issues/7#issuecomment-42659662
.

[chevett]

oic. I believe that's what I'm already doing and I think I can see what needs to change. I'll take a stab at it this weekend and let you know!

[kirbysayshi]

Cool!

Yip yip,
~ Drew*

On Fri, May 9, 2014 at 10:33 AM, Mike Chevett notifications@github.comwrote:

oic. I'm believe that's what I'm already doing and I think I can see what
needs to change. I'll take a stab at it this weekend and let you know!

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/7#issuecomment-42672440
.

[chevett]

Any idea if this has been working? Can this be closed?

[kirbysayshi]

Sorry it took me so long. Yes, it appears to be working! It also revealed a miscalculation on my part. This is what's required to make it work, since now the templates do not share a rendering context:

@* list.vash *@
@{ var item = require('./list-item.vash'); }
<ul>@html.raw(model.map(item))</ul>

As you can see, the return value of the rendering template is needed to be output (via map) and told to not be html escaped. While this makes sense technically, it's a little weird. Still, it works for now.

But either way, your patch looks great!

[chevett]

nice! Keep these kind of things coming. closing.