mustache: support for backtrack path

[wclr]

It seems that can.js doesn't support backtrack paths

{{#person}}{{name}} - {{../company.name}}{{/person}}

https://github.com/wycats/handlebars.js#paths

do you plan to add it?

[moschel]

we need this for loops too, so we can do...

{{#Grid.rows}}
  {{#Grid.cols}}
    <div>{{columnData ../. .}}</div>
  {{/Grid.cols}}
{{/Grid.rows}}

[moschel]

+1 for this. Without this support, here's what I have to do in a helper function to support a nested loop:

Mustache.registerHelper('columnData', function(cols){
    var res = [], col;
    for(var i=0; i<cols.length; i++){
        col = cols[i];
        res.push('<td><div class="yui-dt-liner">');
        res.push(this[col.name + 'Prepared'] ? this[col.name + 'Prepared'] : this[col.name])
        res.push('</div></td>');
    }

    return res.join("");
});

[amcdnl]

@whitecolor In your case you should just be able to do company.name and it should work. Handlebars isn't a full implementation of Mustache so it doesn't support nesting contexts and context jumping like we do.

@moschel Brians case is valid though because if your in a nested loop like that you need the ability to hop up the stack to the parent context.

[justinbmeyer]

Do we have the ability to add things to the context via a helper?

We could have a name or var helper that takes 2 args. The first is the name of a property it will add to the current context, the second is the value.

It could be used like

{{var thing .}}

And then '.' could be referenced as thing in child contexts.

Sent from my iPhone

On Dec 11, 2012, at 2:24 PM, Austin notifications@github.com wrote:

@whitecolor In your case you should just be able to do company.name and it should work. Handlebars isn't a full implementation of Mustache so it doesn't support nesting contexts and context jumping like we do.

@moschel Brians case is valid though because if your in a nested loop like that you need the ability to hop up the stack to the parent context.

—
Reply to this email directly or view it on GitHub.

[justinbmeyer]

+1.

[wclr]

I think it should be put in docs, didn't see it there.