component does not respect can.compute passed via attributes

[wclr]

In latest master:

<my-component blocks="blocks"></my-component>

if blocks is can.compute of parent scope it is not passed to component's scope.

It is because of component.js code (line 105)

var computeData = hookupOptions.scope.computeData(value, {args: []}),
     compute = computeData.compute;
...
initalScopeData[name] = compute();

compute() returns undefined

It worked in previous versions.

[wclr]

Justin, well, actually I hoped that compute would be be passed as a compute function not as value here is a modified test for this:

test("component does not respect can.compute passed via attributes (#540)", function(){

    var data = {
        compute: can.compute(30)
    }

    can.Component.extend({
        tag: "my-component",
        template: "<span>{{blocks}}</span>",

        scope: {
            init: function(){
                // currently this.blocks is just a value of 30
                this.blocks(45)
            }
        }


    })

    var template = can.view.mustache("<my-component blocks='compute'></my-component>");

    var frag  = template(data)

    equal(frag.childNodes[0].childNodes[0].innerHTML, "45")

});

[justinbmeyer]

Yes, but you should still be able to do this.attr('blocks', 45 ). This keeps a component's internal API consistent no matter what you pass it.

[wclr]

Ok, that makes sense.

[wclr]

Don't you think that if component's attr is changed this.attr('blocks', 45 ), then data.compute() value should be updated to? Not it is not, stays the same.