jan/mustache.js - mustache.js - Gitea: Git with a cup of tea

Another rewrite - Cleaner separation of responsibilities in the code between scanning, parsing, compiling, and rendering functions. - Much faster

vor 14 Jahren

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.

vor 6 Jahren

vor 16 Jahren

Another rewrite - Cleaner separation of responsibilities in the code between scanning, parsing, compiling, and rendering functions. - Much faster

vor 14 Jahren

vor 16 Jahren

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.

vor 6 Jahren

12345678

({
  name: 'Chris',
  value: 10000,
  taxed_value: function () {
    return this.value - (this.value * 0.4);
  },
  in_ca: true
});