In FF 3.6.9 the example template doesn t render the nested data structures and the unit tests fail on test 3 onwards.

I m looking at using Handlebars.js in a product at my day-job. Unfortunately, I ve got to get permission from legal, and they won t bless its use without a license. Is there a particular license you re ...

when evaluating a block, handlebars fails if there is no content. eg {{#my_list}}{{/my_list}} or {{^my_list}}{{/my_list}} Not sure if this is a bug, but it would be nice to be able to do.

There should be some sort of rescue or return undefined if a path {{foo/bar}} points to a foo.bar = null. Currently, it just throws an error that there is no bar. There is, it is just null.

I m currently struggling to see the purpose of the first parameter of block helper functions (context). Could you explain how it differs from this? A brief look at the code suggests that what a block ...

I am trying to integrate Handlebars.js into Sammy.js, and I can t get one of Sammy s tests passing. In the test, a partial is used and immediately followed by a normal {{something}}, but Handlebars.js ...

line: Handlebars.compile( num1: {{num1}}, num2: {{num2}} )({num1: 42, num2: 0}); output: num1: 42, num2: output should be: num1: 42, num2: 0

evalExpression is a lot more stable than the attempt at generating array notation for shorter expressions, so we need to use it.

When you use paths inside a section block ({{/some/thing}}), the context is wrong when handlebars calls thing(). See the following code: var templateSrc1 = Testing the context blocks with paths: ...

Memoized paths can sometimes collide with methods on the array object. I updated it to use the following code instead, and it fixed the problem: parsePath: function(path) { if (path == null) { return ...