jan/mustache.js - mustache.js - Gitea: Git with a cup of tea

Another rewrite - Cleaner separation of responsibilities in the code between scanning, parsing, compiling, and rendering functions. - Much faster

14年前

Start linting all test/ files as part of test script (#704) In an effort of ensuring consistent code style in test files as with the "production" source code, we should run eslint as part of the `$ npm test` script as well. Most of the related fixes was done by `eslint` using the `--fix` argument. Only special configuration tweaks for tests compared to the other source code, is to allow functions declaration without names. The rationale for allowing that in tests, is that the important reason we have them in the source code (proper stacktraces) aren't as important in test files.

6年前

don't doublt encode entities. Closes #19. Patch by Leeoniya

16年前

Assert `null` value render It was not being asserted anywhere else, and I was suspecting that PR #552 was changing current (and correct) behaviour.

10年前

Improve HTML escaping. This closes a couple of potential exploit scenarios. Backtick (`) for older IEs and equals (=) for unquoted attributes. Refs https://github.com/wycats/handlebars.js/commit/83b8e846a3569bd366cf0b6bdc1e4604d1a2077e Closes https://github.com/janl/mustache.js/pull/388

10年前

Start linting all test/ files as part of test script (#704) In an effort of ensuring consistent code style in test files as with the "production" source code, we should run eslint as part of the `$ npm test` script as well. Most of the related fixes was done by `eslint` using the `--fix` argument. Only special configuration tweaks for tests compared to the other source code, is to allow functions declaration without names. The rationale for allowing that in tests, is that the important reason we have them in the source code (proper stacktraces) aren't as important in test files.

6年前

1234567

({
  title: function () {
    return 'Bear > Shark';
  },
  symbol: null,
  entities: "&quot; \"'<>`=/"
});