The entry point for Ember Handlebars. This replaces the default Handlebars.compile and turns on template-local data and String parameters.

Lookup both on root and on window. If the path starts with a keyword, the corresponding object will be looked up in the template's data hash and used to resolve the path.

This method uses Ember.Handlebars.get to lookup a value, then ensures that the value is escaped properly.

If unescaped is a truthy value then the escaping will not be performed.

Register a bound helper or custom view helper.

Simple bound helper example

Ember.Handlebars.helper('capitalize', function(value) {
  return value.toUpperCase();
});

The above bound helper can be used inside of templates as follows:

{{capitalize name}}

In this case, when the name property of the template's context changes, the rendered value of the helper will update to reflect this change.

For more examples of bound helpers, see documentation for Ember.Handlebars.registerBoundHelper.

Custom view helper example

Assuming a view subclass named App.CalendarView were defined, a helper for rendering instances of this view could be registered as follows:

Ember.Handlebars.helper('calendar', App.CalendarView):

The above bound helper can be used inside of templates as follows:

{{calendar}}

Which is functionally equivalent to:

{{view App.CalendarView}}

Options in the helper will be passed to the view in exactly the same manner as with the view helper.

A helper function used by registerBoundHelper. Takes the provided Handlebars helper function fn and returns it in wrapped bound helper form.

The main use case for using this outside of registerBoundHelper is for registering helpers on the container:

var boundHelperFn = Ember.Handlebars.makeBoundHelper(function(word) {
  return word.toUpperCase();
});

container.register('helper:my-bound-helper', boundHelperFn);

In the above example, if the helper function hadn't been wrapped in makeBoundHelper, the registered helper would be unbound.

Used for precompilation of Ember Handlebars templates. This will not be used during normal app execution.

Register a bound handlebars helper. Bound helpers behave similarly to regular handlebars helpers, with the added ability to re-render when the underlying data changes.

Simple example

Ember.Handlebars.registerBoundHelper('capitalize', function(value) {
  return Ember.String.capitalize(value);
});

The above bound helper can be used inside of templates as follows:

{{capitalize name}}

In this case, when the name property of the template's context changes, the rendered value of the helper will update to reflect this change.

Example with options

Like normal handlebars helpers, bound helpers have access to the options passed into the helper call.

Ember.Handlebars.registerBoundHelper('repeat', function(value, options) {
  var count = options.hash.count;
  var a = [];
  while(a.length < count) {
      a.push(value);
  }
  return a.join('');
});

This helper could be used in a template as follows:

{{repeat text count=3}}

Example with bound options

Bound hash options are also supported. Example:

{{repeat text count=numRepeats}}

In this example, count will be bound to the value of the numRepeats property on the context. If that property changes, the helper will be re-rendered.

Example with extra dependencies

The Ember.Handlebars.registerBoundHelper method takes a variable length third parameter which indicates extra dependencies on the passed in value. This allows the handlebars helper to update when these dependencies change.

Ember.Handlebars.registerBoundHelper('capitalizeName', function(value) {
  return value.get('name').toUpperCase();
}, 'name');

Example with multiple bound properties

Ember.Handlebars.registerBoundHelper supports binding to multiple properties, e.g.:

Ember.Handlebars.registerBoundHelper('concatenate', function() {
  var values = Array.prototype.slice.call(arguments, 0, -1);
  return values.join('||');
});

Which allows for template syntax such as {{concatenate prop1 prop2}} or {{concatenate prop1 prop2 prop3}}. If any of the properties change, the helper will re-render. Note that dependency keys cannot be using in conjunction with multi-property helpers, since it is ambiguous which property the dependent keys would belong to.

Use with unbound helper

The {{unbound}} helper can be used with bound helper invocations to render them in their unbound form, e.g.

{{unbound capitalize name}}

In this example, if the name property changes, the helper will not re-render.

Use with blocks not supported

Bound helpers do not support use with Handlebars blocks or the addition of child views of any kind.