Putting a can.compute on a Component scope throws

[matthewp]

Will attach a test shortly.

[justinbmeyer]

A "single" value compute like this will blow up, but why would you use that? A function compute should work just fine. prop: can.compute(function(){}).

A Component is probably not necessary. You could probably get this with a map:

can.Map.extend({
  prop: can.compute(false)
})

This probably has to do with compute's clone method.

[matthewp]

That's true, probably no reason to do it this way. One of our existing apps this was working in 2.0.4.

[matthewp]

Tested and this doesn't break on a can.Map.

[daffl]

This changed from 2.0 to 2.1. Closing this issue as it can be fixed by setting it as a property instead of a value compute as discussed.

[justinbmeyer]

I'm not sure it should be closed. It still technically a bug.

[daffl]

Ok. Reopening and putting it int 2.1.3.

[alexisabril]

This was fixed in a prior merge in minor. Typo in the test, adding @matthewp's test to a PR.