Šī lapa labāk darbojas, ja pārlūkam ir iespējots JavaScript.
Sākums
Izpētīt
Palīdzība
Pierakstīties
jan
/
mustache.js
spogulis no
https://github.com/janl/mustache.js
Vērot
1
Pievienot zvaigznīti
0
Atdalīts
0
Kods
Problēmas
0
Laidieni
46
Vikivietne
Aktivitāte
Nevar pievienot vairāk kā 25 tēmas
Tēmai ir jāsākas ar burtu vai ciparu, tā var saturēt domu zīmes ('-') un var būt līdz 35 simboliem gara.
801
Revīzija
19
Atzari
33MB
Koks:
862e497c25
8-as-legacy
master
remove-build-output-from-git
0.4.x
browser-tests-on-8
fix_commonjs
gh-pages
greenkeeper-chai-3.4.0
greenkeeper-chai-4.0.0
greenkeeper-chai-4.0.1
greenkeeper-eslint-1.5.1
greenkeeper-mocha-2.3.3
greenkeeper-mocha-3.3.0
greenkeeper-mocha-3.4.0
greenkeeper-pin
helpers
new-build-system
parser-rewrite
with-js-extras
v4.2.0
v4.1.0
v4.0.1
v4.0.0
v3.2.1
v3.2.0
v3.1.0
v3.0.3
v3.0.2
v3.0.1
v3.0.0
v2.3.2
v2.3.1
v2.3.0
v2.2.1
v2.2.0
v2.1.3
v2.1.2
v2.1.1
v2.1.0
v2.0.0
v1.2.0
v1.1.0
v1.0.0
0.8.2
0.8.1
0.8.0
0.7.3
0.7.2
0.7.1
0.7.0
0.6.0
0.5.2
0.5.2-vsc
0.5.1
0.5.1-vsc
0.5.0-vsc
0.4.2
0.4.1
0.4.0
0.3.0
0.2.3
0.2.2
0.2.1
0.2
0.1
Atzari
Tagi
${ item.name }
Izveidot atzaru
${ searchTerm }
no '862e497c25'
${ noResults }
mustache.js
/
test
/
_files
/
keys_with_questionmarks.js
keys_with_questionmarks.js
42B
Neapstrādāts
Parastais skats
Vēsture
Another rewrite - Cleaner separation of responsibilities in the code between scanning, parsing, compiling, and rendering functions. - Much faster
pirms 14 gadiem
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.
pirms 6 gadiem
add example for section names with question marks
pirms 15 gadiem
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.
pirms 6 gadiem
1
2
3
4
5
({
'person?': {
name: 'Jon'
}
});
