dustjs-linkedin

Dust

This is the LinkedIn fork of Dust.

Getting Started

A quick tutorial for how to use Dust https://github.com/linkedin/dustjs/wiki/Dust-Tutorial

More info http://linkedin.github.io/dustjs/ and http://linkedin.github.io/dustjs/#installation

More

Read more here: http://linkedin.github.com/dustjs/.

For LinkedIn dust-helpers: https://github.com/linkedin/dustjs-helpers.

For LinkedIn secure-filters : https://github.com/linkedin/dustjs-filters-secure.

Building Dust locally

Grab a copy of the repo

cd some_project_directory
git clone https://github.com/linkedin/dustjs.git dustjs
cd dustjs

(Optional) Install Grunt-cli

• Grunt-cli lets you run Grunt from within a subfolder see http://gruntjs.com/getting-started

npm install -g grunt-cli

Fetch all node dependencies

npm install

Run tests

grunt test

Contributing to Dust

• Setup a branch for what you are working on

    git checkout -b myBranchName
  

• Test your changes (jshint, unit tests in node, rhino and phantom and make sure test coverage thresholds are met)

    grunt test
  

• Use grunt dev while developing\debugging. This task will start a server and serve Jasmine spec runner on http://localhost:3000/_SpecRunner.html. This task uses unminified dust-full.js so it allows you to easily step through the code in a browser.

• Use grunt testClient to test production version of code (dust-full.min.js) in a browser. Similarly to grunt dev it serves Jasmine spec runner on http://localhost:3000/_SpecRunner.html.

• Add unit tests. Unit tests can be found in the test/jasmine-tests/spec directory. Help us keep up good test coverage! To view coverage report run grunt coverage and open tmp/coverage/index.html in a browser.

• Add an issue and send a pull request. Pull requests are easier to track if you also include an issue. Sending a pull request from a branch makes it easier for you to resolve conflicts in master

Changelog

v2.6.0 (2015/03/05 01:30 +00:00)

• #545 New dustc compiler. This breaks backward compat, but allows streaming output and a usage manual. Also includes tests that were nonexistent previously. (@sethkinast)
• #536 Add AMD (require.js) compatibility. This includes the core, compiler, parser, and support for compiling templates as AMD modules. Have to set define.amd.dust to true to allow dust to be loaded as an AMD module, and dust.config.amd to true to compile templates as AMD modules. (@sethkinast)
• #543 dustc: replace util.print/util.puts with console.log (@hunterchristian)
• #541 Escape template names in case they contain non-JS-safe characters (@aredridel)
• #540 escape values (\u2028, \u2029 and <) when using json filter (@jimmyhchan)
• #534 Stringify things before calling escapeHtml on them in case their stringified representation contains HTML (@sethkinast)
• #537 Stop archiving old releases (@sethkinast)
• #533 Add dust.version and bump it during grunt-bump (@sethkinast)
• #529 Fix hanging comma in dust.config. Fixes IE7. (@jrrbru)
• #526 Don't stringify dust.log messages (@sethkinast)