resolve . notation about plates HOT 6 CLOSED

`

from plates.

Good point. One should treat . notation as a last resort.

from plates.

Another issue that will arrise in some templates is the notion of a transformation of the data during the binding process, this ultimately winds up being a function call. For example:

function fullName() { return this.firstName + ' ' + this.lastName; }

I can't find my test case right now but it leverages the valueOf operator

var person_prototype = {
    fullName: { valueOf: function() { return this.firstName + ' ' + this.lastName; } }
}

var person = {
    firstName: 'First',
    lastName: 'Last'
}

I prefer to keep this logic outside of the template if possible, this could also be extended so the function has access to the Lightweight DOM and then you have every single edge case nailed without any special template syntax.

from plates.

Hmm. I think this should be done at the data level, not at the template level. It is probably equally fast to run over the data set and apply the function there before running it through plate.

from plates.

I'm not a fan of touching the data, it could be cached and could also be in use by multiple templates, I do however like the idea of extension functions over the data, even if it's not really prototyped, this could just be a little magic behind the scenes.

Will hack together a working example for data transformation and template nesting using the pseudo code posted on the nesting issue and see how it feels.

from plates.

Dot-notation should work anyway (there was bug in a parser), fixed in e58a836 .

Thanks

from plates.