jan
/
mustache.js
zrcadlo https://github.com/janl/mustache.js
Sledovat 1
Oblíbit 0
Rozštěpit 0
Zdrojový kód Úkoly 0 Vydání 46 Wiki Aktivita
Nelze vybrat více než 25 témat Téma musí začínat písmenem nebo číslem, může obsahovat pomlčky („-“) a může být dlouhé až 35 znaků.
821 Revize
19 Větve
33MB
Strom: ea3adcfc93
Větve Značky
${ item.name }
Vytvořit větev ${ searchTerm }
z „ea3adcfc93“
${ noResults }
mustache.js/test/_files/keys_with_questionmarks.js

keys_with_questionmarks.js 42B
Surový Normální zobrazení Historie

Another rewrite - Cleaner separation of responsibilities in the code between scanning, parsing, compiling, and rendering functions. - Much faster
před 14 roky
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.
před 6 roky
​
add example for section names with question marks
před 15 roky
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.
před 6 roky
 12345 
  1. ({

  2.   'person?': {

  3.     name: 'Jon'

  4.   }

  5. });