can.List compute properties

[moschel]

It seems there is an inconsistency in how can.Map properties and can.List properties can be defined as computes. After defining a compute in can.Map, it can be referenced with obj.attr('computePropName'), but for can.List instances, list.attr('computePropName') returns a function, not the result of the compute.

Person = can.Map.extend({
    speak: can.compute(function(){
        return "foo"
    })
})
var p = new Person();
console.log('map speak', p.attr('speak'))

People = can.List.extend({
    speak: can.compute(function(){
        return "foo"
    })
})
var list = new People([1, 2, 3]);
console.log('map speak', list.attr('speak'));

outputs the following:

map speak foo 
map speak function (c){if(arguments.length){var b=q,e=w.call(d,c,b);if(m.hasDependencies)return r.call(d);q=void 0===e?r.call(d):e;b!==q&&a.batch.trigger(m,
"change",[q,b]);return q}a.__reading&&y&&(a.__reading(m,"change"),p.bound||a.compute.temporarilyBind(m));return p.bound?q:r.call(d)} 

[justinbmeyer]

I think this is a duplicate issue.

Sent from my iPhone

On Mar 14, 2014, at 1:18 AM, Brian Moschel notifications@github.com wrote:

It seems there is an inconsistency in how can.Map properties and can.List properties can be defined as computes. After defining a compute in can.Map, it can be referenced with obj.attr('computePropName'), but for can.List instances, list.attr('computePropName') returns a function, not the result of the compute.

Person = can.Map.extend({
speak: can.compute(function(){
return "foo"
})
})
var p = new Person();
console.log('map speak', p.attr('speak'))

People = can.List.extend({
speak: can.compute(function(){
return "foo"
})
})
var list = new People([1, 2, 3]);
console.log('map speak', list.attr('speak'));
outputs the following:

map speak foo
map speak function (c){if(arguments.length){var b=q,e=w.call(d,c,b);if(m.hasDependencies)return r.call(d);q=void 0===e?r.call(d):e;b!==q&&a.batch.trigger(m,
"change",[q,b]);return q}a.__reading&&y&&(a.__reading(m,"change"),p.bound||a.compute.temporarilyBind(m));return p.bound?q:r.call(d)}
—
Reply to this email directly or view it on GitHub.

[isadovskiy]

I'm interesting in the answer too.