Chinaunix首页 | 论坛 | 博客
  • 博客访问: 53184
  • 博文数量: 48
  • 博客积分: 0
  • 博客等级: 民兵
  • 技术积分: 260
  • 用 户 组: 普通用户
  • 注册时间: 2016-07-12 11:48
文章分类
文章存档

2016年(48)

我的朋友

分类: JavaScript

2016-11-04 16:01:20

koahub-handlebars

koahub-handlebars

koahub handlebars templates

Helpers are registered using the #registerHelper method. Here is an example using the default instance (helper stolen from official Handlebars :

点击(此处)折叠或打开

  1. hbs = require('koahub-handlebars');
  2.  
  3. hbs.registerHelper('link', function(text, url) {
  4.   text = hbs.Utils.escapeExpression(text);
  5.   url = hbs.Utils.escapeExpression(url);
  6.  
  7.   var result = '+ url + '">' + text + '';
  8.  
  9.   return new hbs.SafeString(result);
  10. });

Your helper is then accessible in all views by using, {{link "Google" ""}}

The registerHelper, Utils, and SafeString methods all proxy to an internal Handlebars instance. If passing an alternative instance of Handlebars to the middleware configurator, make sure to do so before registering helpers via the koahub-handlebars proxy of the above functions, or just register your helpers directly via your Handlebars instance.

You can also access the current Koa context in your helper. If you want to have a helper that outputs the current URL, you could write a helper like the following and call it in any template as {{requestURL}}.

点击(此处)折叠或打开

  1. hbs.registerHelper('requestURL', function() {
  2.   var url = hbs.templateOptions.data.koa.request.url;
  3.   return url;
  4. });

The simple way to register partials is to stick them all in a directory, and pass the partialsPath option when generating the middleware. Say your views are in ./views, and your partials are in ./views/partials. Configuring the middleware via

点击(此处)折叠或打开

  1. app.use(hbs.middleware({
  2.   viewPath: __dirname + '/views',
  3.   partialsPath: __dirname + '/views/partials'
  4. }));

will cause them to be automatically registered. Alternatively, you may register partials one at a time by calling hbs.registerPartial which proxies to the cached handlebars #registerPartial method.

Passing defaultLayout with the a layout name will cause all templates to be inserted into the {{{body}}} expression of the layout. This might look like the following.

点击(此处)折叠或打开

  1. <!DOCTYPE html>
  2. <html>
  3. <head>
  4.   <title>{{title}}</title>
  5. </head>
  6. <body>
  7.   {{{body}}}
  8. </body>
  9. </html>

In addition to, or alternatively, you may specify a layout to render a template into. Simply specify {{!< layoutName }} somewhere in your template. koahub-handlebars will load your layout from layoutsPath if defined, or from viewPath otherwise.

At this time, only a single content block ({{{body}}}) is supported.

The plan for koahub-handlebars is to offer identical functionality as koa-hbs (eventaully). These options are supported now.

  • viewPath: [required] Full path from which to load templates (Array|String)
  • handlebars: Pass your own instance of handlebars
  • templateOptions: Hash of handlebars options to pass to template()
  • extname: Alter the default template extension (default: '.html')
  • partialsPath: Full path to partials directory (Array|String)
  • defaultLayout: Name of the default layout
  • layoutsPath: Full path to layouts directory (String)
  • disableCache: Disable template caching (default: '.true')

Application local variables ([this.state]()) are provided to all templates rendered within the application.

点击(此处)折叠或打开

  1. app.use(function *(next) {
  2.   this.state.title = 'My App';
  3.   this.state.email = 'me@myapp.com';
  4.   yield next;
  5. });

The state object is a JavaScript Object. The properties added to it will be exposed as local variables within your views.

点击(此处)折叠或打开

  1. <title>{{title}}</title>
  2. <p>Contact : {{email}}</p>

  1. Configuration file incremental changes
  2. Modify some of the features and the default configuration
  3. ...

 

wemall 开源微商城 ,微信商城,商城源码,三级分销,微生鲜,微水果,微外卖,微订餐---专业的o2o系统
wemall地址:
代码地址:

阅读(546) | 评论(0) | 转发(0) |
给主人留下些什么吧!~~