jan
/
mustache.js
Mirror von https://github.com/janl/mustache.js
Beobachten 1
Favorisieren 0
Fork 0
Code Issues 0 Releases 46 Wiki Aktivität
Du kannst nicht mehr als 25 Themen auswählen Themen müssen entweder mit einem Buchstaben oder einer Ziffer beginnen. Sie können Bindestriche („-“) enthalten und bis zu 35 Zeichen lang sein.
838 Commits
19 Branches
33MB
Struktur: f1e546c284
Branches Tags
${ item.name }
Erstelle Branch ${ searchTerm }
von „f1e546c284“
${ noResults }
mustache.js/test/_files/escaped.js

escaped.js 108B
Originalformat Normale Ansicht Verlauf

Another rewrite - Cleaner separation of responsibilities in the code between scanning, parsing, compiling, and rendering functions. - Much faster
vor 14 Jahren
​
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.
vor 6 Jahren
don't doublt encode entities. Closes #19. Patch by Leeoniya
vor 16 Jahren
Assert `null` value render It was not being asserted anywhere else, and I was suspecting that PR #552 was changing current (and correct) behaviour.
vor 10 Jahren
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
vor 10 Jahren
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.
vor 6 Jahren
 1234567 
  1. ({

  2.   title: function () {

  3.     return 'Bear > Shark';

  4.   },

  5.   symbol: null,

  6.   entities: "&quot; \"'<>`=/"

  7. });