jan
/
mustache.js
镜像来自 https://github.com/janl/mustache.js
關注 1
收藏 0
複製 0
程式碼 問題 0 版本發佈 46 Wiki 活動
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
830 提交
19 分支
33MB
分支: master
分支列表 標籤
${ item.name }
建立分支 ${ searchTerm }
從 'master'
${ noResults }
mustache.js/test/_files/empty_string.js

empty_string.js 73B
原始文件 永久連結 Normal View 歷史記錄

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. });