Ember is migrating to a non-context switching #each helper. For a patibility piece I need to do the same from raw handlebars.

However the trivial attempt fails

var f = Handlebarspile("{{#each numbers}}{{this}}{{/each}}");
console.log(f({numbers: [1,2,3]}));
// works

var f2 = Handlebarspile("{{#each number in numbers}}{{number}}{{/each}}");
console.log(f2({numbers: [1,2,3]}));
// fails

How do I get {{#each number in numbers}} to work in raw handlebars 2.0?

EDIT

Added a bounty here, for a handlebars extension based off .js that gives us each.. in support. It is clear its not built into handlebars. It is also clear Ember is able to extend this.

Ember is migrating to a non-context switching #each helper. For a patibility piece I need to do the same from raw handlebars.

However the trivial attempt fails

var f = Handlebars.pile("{{#each numbers}}{{this}}{{/each}}");
console.log(f({numbers: [1,2,3]}));
// works

var f2 = Handlebars.pile("{{#each number in numbers}}{{number}}{{/each}}");
console.log(f2({numbers: [1,2,3]}));
// fails

How do I get {{#each number in numbers}} to work in raw handlebars 2.0?

EDIT

Added a bounty here, for a handlebars extension based off https://github./discourse/discourse/blob/master/app/assets/javascripts/discourse/lib/ember_pat_handlebars.js that gives us each.. in support. It is clear its not built into handlebars. It is also clear Ember is able to extend this.

• javascript
• ember.js
• handlebars.js

• I think its a bug. Even if we use Em.Handlebars.pile, if give an error 'Cannot read property 'controller' of undefined' – blessanm86 Commented Jan 5, 2015 at 2:59
• Ember's prepiled functions expect additional context that isn't provided by just passing in the hash. It's expecting views, containers, controllers, the works. – Kingpin2k Commented Jan 5, 2015 at 3:02

4 Answers 4

This shows how it can be done. But note that it requires the stringParams flag at pile time, which changes the way all helpers get called, so this will probably break all the other helpers unless you provide stringParams patible versions of them.

Handlebars.registerHelper('each', function(localName,inKeyword,contextName,options){
  var list = this[contextName];
  var output = "";
  var innerContext = Object.create(this);
  for (var i=0; i<list.length; i++) {
    innerContext[localName] = list[i];
    output += options.fn(innerContext);
  }
  return output;
});

 var f = Handlebars.pile("{{#each number in numbers}}{{number}}{{/each}}", {
  stringParams: true
});

console.log(f({numbers: [1,2,3]}));

The non-context switching each helper is a helper introduced in Ember, it isn't part of the core handlebars library. You won't be able to use it with plain ol' handlebars.

If I understand you question correctly, I believe this will work.

var hbs = "{{#each this}}{{this}}{{/each}}";
var f3 = Handlebars.pile(hbs);
console.log(f3({numbers: [1,2,3]}));
console.log(f3({numbers: [3,2,1]}));

http://jsbin./tebayupobu/4/edit

Perhaps you don't need to implement this at all since Handlebars is moving to block parameters for non context switching helpers. Ember is already using block params in 1.10 Beta (you can read about block params in the release notes).

You can use the latest builds of Handlebars to get the non context switching each with the new block params syntax right now:

var f = Handlebars.pile("{{#each numbers}}{{this}}{{/each}}");
console.log(f({numbers: [1,2,3]}));

var f = Handlebars.pile("{{#each numbers as |number|}}{{number}}{{/each}}");
console.log(f({numbers: [1,2,3]}));

Console:

"123"
"123"

Updated JSBin with the new syntax.