jan
/
mustache.js
şunun yansıması https://github.com/janl/mustache.js
İzle 1
Yıldızla 0
Çatalla 0
Kod Konular 0 Sürümler 46 Wiki Aktivite
25'ten fazla konu seçemezsiniz Konular bir harf veya rakamla başlamalı, kısa çizgiler ('-') içerebilir ve en fazla 35 karakter uzunluğunda olabilir.
737 İşlemeler
19 Dallar
33MB
Ağaç: bb700c5433
Dallar Biçim İmleri
${ item.name }
Branş ${ searchTerm } oluştur
'bb700c5433'den
${ noResults }
mustache.js/test/_files/empty_string.js

empty_string.js 73B
Ham Normal Görünüm Geçmiş

Another rewrite - Cleaner separation of responsibilities in the code between scanning, parsing, compiling, and rendering functions. - Much faster
14 yıl önce
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 yıl önce
Add spec for empty string (issue #94)
14 yıl önce
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 yıl önce
Add spec for empty string (issue #94)
14 yıl önce
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 yıl önce
 123456 
  1. ({

  2.   description: 'That is all!',

  3.   child: {

  4.     description: ''

  5.   }

  6. });