jan
/
mustache.js
의 미러 https://github.com/janl/mustache.js
보기 1
좋아요 0
포크 0
코드 이슈 0 릴리즈 46 위키 활동
25개 이상의 토픽을 선택하실 수 없습니다. Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
830 커밋
19 브랜치
8.1MB
브렌치: master
브랜치 태그
${ item.name }
${ searchTerm } 브랜치 생성
from 'master'
${ noResults }
mustache.js/test/_files/empty_string.js

empty_string.js 73B
Raw 고유링크 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. });