jan
/
mustache.js
дзеркало https://github.com/janl/mustache.js
Слідкувати 1
В обрані 0
Форк 0
Код Проблеми 0 Релізи 46 Вікі Активність
Ви не можете вибрати більше 25 тем Теми мають розпочинатися з літери або цифри, можуть містити дефіси (-) і не повинні перевищувати 35 символів.
830 Коміти
19 Гілки
8.1MB
Дерево: 972fd2b27a
Гілки Теги
${ item.name }
Створити гілку ${ searchTerm }
з '972fd2b27a'
${ noResults }
mustache.js/test/_files/empty_string.js

empty_string.js 73B
Неформатований Звичайний вигляд Історія

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 роки тому
Add spec for empty string (issue #94)
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 роки тому
Add spec for empty string (issue #94)
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 роки тому
 123456 
  1. ({

  2.   description: 'That is all!',

  3.   child: {

  4.     description: ''

  5.   }

  6. });