Seth Kinast
Seth Kinast
We'd still like to do this; I have some thoughts on it once I get time to work on dust core.
``` if (!dust.isEmptyObject(params)) { partialContext = partialContext.clone(); head = partialContext.pop(); partialContext = partialContext.push(params) .push(head); } ``` Partial context gets inserted behind the context head. @jimmyhchan what's the legacy reason for...
https://github.com/linkedin/dustjs/issues/313 here we go. I think we should probably just change this in Dust@3
OK, more insight. I haven't read this part of the code in a bit. The code for **sections** looks like this: Push section params onto the stack If iterating over...
However that prevents `{.}` from working properly because of traversal structure. Complex...
I really want to build "gust" (it's gist for Dust!) but just so many projects... On Tue, Feb 16, 2016 at 7:03 PM Matt Edelman [email protected] wrote: > Perhaps this...
I wonder if I could fork an existing gistable repl like Babel's and just hack something up that way. On Tue, Feb 16, 2016 at 7:39 PM Matt Edelman [email protected]...
OK, so a standalone module would be best. It honestly would be pretty fun to build, maybe we can get some traction on it.
@smfoote can you peek at this?
Yeah I think it's definitely just the component, that was why I thought you might know best how to handle it. It's just a self xss so not critical, no...