strange behavior for {{foo.bar}} when foo is 0 or null or false

[zordius]

• Tests on current , http://builds.handlebarsjs.com.s3.amazonaws.com/handlebars-c90cfe2.js :
  http://jsfiddle.net/WxK6S/2/
  foo.bar got 0 when foo == 0
• Tests on 1.1.1 , http://builds.handlebarsjs.com.s3.amazonaws.com/handlebars-v1.1.1.js :
  http://jsfiddle.net/WxK6S/3/
  foo.bar got undefined when foo == 0

This may related with #731

[kpdecker]

How is this issue different from #731?

[zordius]

#731 related with context change by {{#foo}} , and this is related with dot resolve {{foo.bar}} ?

No matter 0 is true or false or anything else , I think {{foo.bar}} always will be undefined when input do not provide foo.bar , and no matter foo == anything.

[kpdecker]

Gotcha, thanks for the clarification.

Yes {{foo.bar}} should evaluate to undefined when foo is 0. It does not appear that the fix for #731 resolved this so we'll have to look at this case as well.

  it('GH-820: zero pathed rendering', function() {
    shouldCompileTo('{{foo.bar}}', {foo: 0}, '');
  });

[kpdecker]

Released in v2.0.0-beta.1