Path accessor to prevent walking up the scope

[daffl]

There are some valid use cases where walking up the scope for a property lookup is not what you want. For example:

{
  title: 'CanJS school',
  children: [{
    name: 'first'
  }, {
    name: 'second',
    title: 'Second title'
  }]
}

And

{{#each children}}
  <p>{{title}}</p>
{{/each}}

Will render CanJS school as the first item. The best solution is probably prefixing the property name with a ./ accessor if you don't want it to be looked up in the parent scope:

{{#each children}}
  <p>{{./title}}</p>
{{/each}}

[stevenvachon]

Is {{#each children}} supposed to simulate {{#children}} to begin with? I'd have thought that a {{#with children}} would be necessary.

[matthewp]

@stevenvachon You can use either #each children or #children for arrays.

As for the issue, personally I would rather fix this issue in JavaScript rather than adding the complexity of paths to mustache.

[savinger]

@matthewp Is there some straightforward way to fix this in javascript beyond renaming attributes? I have handlebars templates that I'm trying to transition to mustache right now that render something inherently recursive. So this abstract object can have one or more similar objects within it, so they all share the same attributes, but each does not necessarily have all. All that to say renaming isn't really an option.

Just hoping that may motivate the issue a bit.

[stevenvachon]

@matthewp

Yes, but I was referring to the context change. #each and #key do behave the same in this regard, though, despite my guessing otherwise.

Also, I'm not so sure that it can be fixed in JavaScript. #each is behaving correctly by referencing its parent scope when it cannot find a variable.

[matthewp]

Talked this over off-issue, I wasn't aware that ../ already exists so I withdraw my objection. @savinger

[daffl]

Fixed via #874