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.
751 Révisions
19 Branches
33MB
Aborescence: d820d254e5
Branches Tags
${ item.name }
Créer la branche ${ searchTerm }
de 'd820d254e5'
${ noResults }
mustache.js/test/_files/higher_order_sections.js

higher_order_sections.js 190B
Brut Vue normale Historique

Another rewrite - Cleaner separation of responsibilities in the code between scanning, parsing, compiling, and rendering functions. - Much faster
il y a 14 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
​
Another rewrite - Cleaner separation of responsibilities in the code between scanning, parsing, compiling, and rendering functions. - Much faster
il y a 14 ans
​
Text passed to higher-order sections unrendered Fixes #187
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
Another rewrite - Cleaner separation of responsibilities in the code between scanning, parsing, compiling, and rendering functions. - Much faster
il y a 14 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
 123456789 
  1. ({

  2.   name: 'Tater',

  3.   helper: 'To tinker?',

  4.   bolder: function () {

  5.     return function (text, render) {

  6.       return text + ' => <b>' + render(text) + '</b> ' + this.helper;

  7.     };

  8.   }

  9. });