mustache.js

750 提交

19 分支

17MB

目录树: 944f3611e8

提交图

作者	SHA1	备注	提交日期
Phillip Johnsen	bb700c5433	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 年前
Michael Jackson	5ab345eddf	Use JavaScript's definition of falsy Fixes #186	13 年前

作者

SHA1

备注

提交日期

Phillip Johnsen

bb700c5433

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 年前

Michael Jackson

5ab345eddf

Use JavaScript's definition of falsy

Fixes #186

13 年前

2 次代码提交 (944f3611e8f09465cce29f44e2c1e7fad832a14c)