jan
/
mustache.js
miroir de https://github.com/janl/mustache.js
Suivre 1
Ajouter aux favoris 0
Bifurcation 0
Code Tickets 0 Versions 46 Wiki Activité
Vous ne pouvez pas sélectionner plus de 25 sujets Les noms de sujets doivent commencer par une lettre ou un nombre, peuvent contenir des tirets ('-') et peuvent comporter jusqu'à 35 caractères.
822 Révisions
19 Branches
21MB
Aborescence: cc66a7084a
Branches Tags
${ item.name }
Créer la branche ${ searchTerm }
de 'cc66a7084a'
${ noResults }
mustache.js/test/_files/check_falsy.js

check_falsy.js 119B
Brut Vue normale Historique

Don't evaluate lambdas that return falsy values as an empty string. Issue: If I create a Mustache lambda to return numbers and I expect 0 to be of those numbers, I'll instead only receive an empty string for 0 because it evaluates to falsy. Fix: Check the result of the lambda to be undefined or null. Only then should it return the empty string.
il y a 13 ans
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.
il y a 6 ans
​
Don't evaluate lambdas that return falsy values as an empty string. Issue: If I create a Mustache lambda to return numbers and I expect 0 to be of those numbers, I'll instead only receive an empty string for 0 because it evaluates to falsy. Fix: Check the result of the lambda to be undefined or null. Only then should it return the empty string.
il y a 13 ans
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.
il y a 6 ans
Don't evaluate lambdas that return falsy values as an empty string. Issue: If I create a Mustache lambda to return numbers and I expect 0 to be of those numbers, I'll instead only receive an empty string for 0 because it evaluates to falsy. Fix: Check the result of the lambda to be undefined or null. Only then should it return the empty string.
il y a 13 ans
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.
il y a 6 ans
 1234567 
  1. ({

  2.   number: function (text, render) {

  3.     return function (text, render) {

  4.       return +render(text);

  5.     };

  6.   }

  7. });