dustjs
dustjs copied to clipboard
linkedin
Asynchronous Javascript templating for the browser and server
Replaces #354 since we removed the old `dustc` tool. We will create a command-line tool that accepts a template and context, and renders the result to stdout or a file....
Some sort of small HTML (web component? probably not) that we can apply to documentation. ``` Dust allows Promises to be passed as part of your context. When a Promise...
The Get Dust page only shows how to `npm install` dust-helpers. We should include bower instructions, as well as a link to the dust helpers repo.
We suffer badly from copy-paste divergence across testing frameworks in dust and dust-helpers. We need to modularize that code and pull it out into a package that includes the Rhino...
It's probably best if we use a shootout engine that already exists somewhere, and make it part of a testing suite. That keeps us from having to dep a bunch...
Preferably a meta description that is unique for each page.
Given a context like this: ``` js { "bar": "fubar", "helper": function(chunk, context, bodies, params) { return chunk.write(params.foo); } } ``` and a template like this: ``` html {#helper foo="{bar}"/}...
Using the following template: ``` html {! :tabSize=2:indentSize=2:mode=html: !} {! The form for help/about !} Help / About This is version {version} of the interface, with version {backend_version} of the...
Dust templates currently compile to a set of functions that are invoked via `body_0` being registered by `dust.register`. In #513 we suggest that these body functions could be members of...
Hi there, you are most likely aware of this, but I'm filing this as an issue anyway. As you point out in the wiki (https://github.com/linkedin/dustjs/wiki/Dust-Tutorial#Parameter_rules) params will overlay the context...
