实现来自于： https://github.com/component/escape-html ，增加了 xtemplate 里面会转义的字符。

before:

no special characters    x 22,928,859 ops/sec ±0.98% (191 runs sampled)
single special character x  1,926,023 ops/sec ±0.83% (187 runs sampled)
many special characters  x    687,743 ops/sec ±0.98% (187 runs sampled)

after:

no special characters    x 22,687,378 ops/sec ±0.79% (192 runs sampled)
single special character x  6,571,191 ops/sec ±1.33% (190 runs sampled)
many special characters  x  3,465,183 ops/sec ±1.01% (191 runs sampled)

here is an example:

data

{
  ‘startDate': 'Wed Nov 02 2016 14:07:56 GMT+0800 (CST)'
}

xtpl (pass data as root):

{{set (startDate = $utils.moment('Wed Nov 02 2016 14:07:56 GMT+0800 (CST)', 'YYYY-MM-DD hh:mm:ss').toDate())}}
{{startDate.getTime()}}

it will retrieve startDate from origin data, not affix

现在 each 来做循环，会有一个新的 scope，但是感觉语义上有点纠结，例如：

{{set (pic = "out side pic")}}
{{set (array = [{
  "title": "inside title 1",
  "pic": "inside pic 1"
}, {
  "title": "inside title 2"
}])}}

{{# each (array) }}
{{title}}{{pic}}
{{/ each }}

让人觉得比较晕。

是否可以考虑加一个类似 for in 的循环：

{{# for item in array }}
{{item.title}}{{item.pic}}
{{/ for }}

gulp.task('xtpl', ['clean'], function() {
  gulp.src(paths.xtpl)
    .pipe(gulpXTemplate({
      wrap: 'kissy', // defaults to modulex. set to define compiled to define() or kissy to KISSY.add
      compileConfig: {
        isModule: 1, // defaults to 1. use native template require
        catchError: false // defaults to false. whether to point to line of xtpl when exception occurs(impact performance)
      },
      // runtime:'', defaults to kg/xtemplate/x.y.z/runtime
      suffix: '.xtpl', // defaults to .xtpl. transform xx.tpl -> xx.js
      truncatePrefixLen: 0, //optional, remove the first length string of file path from generate code
      XTemplate: XTemplate // required. xtemplate module
    }))
    // .pipe(uglify()) 
    .pipe(gulp.dest('build'))
});

使用 CMD 代码组织方式 比如文件 a-render.js 在 config.debug = false 的情况下.

require 会自动引用 a-render-min.js 经过 uglify 后的代码无法运行了

类似以下的写法，一旦skuProps下不存在skuProps是极容易出问题，定位问题时也较为困难，这也是ES5有严格模式的初衷之一

{{#with (skuProps)}}
    {{#each (skuProps)}}

同样xtemplate也可考虑支持下严格模式，此时使用with就会报错，提示当前为严格模式，不能使用with：

xTemplate.strict = true;

current compiled code

a.xtpl

{{include('./b')}}{{x}}

a.js

function(){
  params2.push('./b-xtpl');
  config1.params = params2;
  if(moduleWrap){
     require('./b-xtpl');
  }
}

optimized compiled code

a.xtpl

{{include('./b')}}{{x}}

a.js

function(){
 var submodule;
 if(moduleWrap){
     submodule = require('./b-xtpl');
 }
 params2.push(submodule  && submodule.TPL_NAME||'./b-xtpl');
 config1.params = params2;
}

demo： https://github.com/ngot/xtpl-win-test

travis：https://travis-ci.org/ngot/xtpl-win-test/builds/210846134

appveyor： https://ci.appveyor.com/project/ngot/xtpl-win-test

linux&mac不复现，windows能够复现。

windows日志：

pathName: C:\projects\xtpl-win-test\view\home.xtpl
pathName: header.xtpl

linux日志：

pathName: /home/travis/build/ngot/xtpl-win-test/view/home.xtpl
pathName: /home/travis/build/ngot/xtpl-win-test/view/header.xtpl

describe('whitespace control', function () {
  it('ltrim works',function(){
    var tpl = [
      ' ',
      '{{~"x"}}',
      ' '
    ].join('');
    var ret = new XTemplate(tpl).render({});
    expect(ret).to.equal('x ');
  });

  it('rtrim works',function(){
    var tpl = [
      ' ',
      '{{ "x" ~}}',
      ' '
    ].join('');
    var ret = new XTemplate(tpl).render({});
    expect(ret).to.equal(' x');
  });

  describe('block',function(){
    it.only('works inside block',function(){
      var tpl=[
        '{{#each(data)~}}',
        '{{this}}',
        '{{~/each}}'
      ].join('\n');
      var ret = new XTemplate(tpl).render({
        data:[1,2,3]
      });
      expect(ret).to.equal('123');
    });
  });
});

In our project, we want to download xtemplate via bower ( or npm ) in local.

Could you please add dist folder by default, so that we can use the download-version without manually build in bower_components (or node_modules) folder.

expect(function () {
      var tpl = '{{obj.error}}\n{{obj.error()}}';
      new XTemplate(tpl).render({
        obj: {
          error: error
        }
      });
    }).to.throwException(function (e) {
    expect(e.message).to.match(/Execute function `obj.error` Error: mock error/);
    expect(e.message).to.match(/line 2/);
  });

新语法需求

list.xtpl，某一个列表模块作为一个独立模板

{{#each(list)}}
  <a href="{{url}}">{{title}}</a><br>
{{/each}}

page.xtpl, 在页面中引用刚刚的模块

{{set (array = [{
  "url": "",
  "title": ""
}])}}

{{ includeSection ("list.xtpl", array) }}

希望能增加上面类似includeSection的功能。

vs macro与include

1. macro必须要有函数名以及参数，但实际使用时我们往往希望是一个文件即为一个模块，可直接引用文件；
2. 相对于include， "includeSection"可以传递数据到目标模块，并在内部完成渲染。include返回的是xtpl, "includeSection"返回的是html.

"includeSection"使用起来比macro更加简单方便。 举个例子，调用一个模块： 使用macro

{{#macro("list", "array")}}
  {{#each(array)}}
    <a href="{{url}}">{{title}}</a><br>
  {{/each}}
{{/macro}}

{{include ("../shared/list")}}
{{macro("list", array)}}

使用"includeSection"

 {{#each(array)}}
   <a href="{{url}}">{{title}}</a><br>
 {{/each}}

{{includeSection ("../shared/list", array)}}

{{ set (metaPageData = {"backgroundImg":{"url":"222","name":"1.png"}}) }}

以上模板会报错

VM119 seed-min.js:31 Uncaught Error: XTemplate error in file: xtemplate1 syntax error at line 1:
....png","name":"1.png"}}) }}
-----------------------^
expect reduce:R_BRACE, reduce:COMMA

使得可以在模板渲染前增加统一的模板处理，可以放在config配置项内

  if (tplType === 'string') {

    /*------------------------------------------------------------*/
    /* 增加beforeCompile回调 */
    if(typeof config.beforeCompile === 'function'){
      tpl = config.beforeCompile(tpl);
    }
    /*------------------------------------------------------------*/

    try {
      tpl = this.compile(tpl, config.name);
    } catch (err) {
      this.compileError = err;
    }
  }