Steven

As far as I can tell, there is an error in how the demo web component is escaping HTML in the JSON. I don't believe this is an XSS hole...

It's a weird one, and now I'm curious.

@shchekoldin This looks like a good solution, at least in the short term.

I think this is possible now using string interpolation in partial names: Content partial (named "innerComponent"): ``` Hello world ``` Main partial (named "component"): ``` {>"{contentPartial}"/} ``` Usage: ``` {>component...

Alright, what you want is a custom Dust helper (see http://www.dustjs.com/guides/dust-helpers/ and http://www.dustjs.com/docs/helper-api/ for more info on writing custom helpers). For the form.dust example above, here's more or less what...

Looks like you need to `git pull` before we try to merge.

Does this work with two separate partials? ``` {! base.tl !} {+partial url=search_url/} ``` ``` {! override.tl !} {>"base.tl"/} {

I actually like the idea of a `renderTo` method. Though it is just sugar, I think it's really nice sugar. ``` dust.renderTo(tmpl, ctx, el).then(() => attachEventListeners); ``` That would be...

I know it won't, but it would be pretty great.

That seems reasonable