can.Map method not become computable automatically

[isadovskiy]

Please check this minimalistic example: http://jsfiddle.net/jd44f/6/

My expectation is everything should work without wrapping team.shortName method with can.compute().

Reproduced with CanJS 2.1.2

[isadovskiy]

Ok, got another example which could give some glue for Bitovi team: http://jsfiddle.net/jd44f/7/

[gsmeets]

Use the define get methode instead of just properties on the prototype.

[isadovskiy]

Yes, it will be work around for this issue.

This post were made as bug report for future releases.

[gsmeets]

I don't think this is a bug. The normal" prototype properties are there for simple observables, computed properties like the one you're building should be done with the define plugin.

[isadovskiy]

Please check this example: http://jsfiddle.net/jd44f/7/. It's a bug...

As for define plugin, it's just an optional plugin, which can be omitted at all.

[isadovskiy]

Here is an example without define plugin: http://jsfiddle.net/jd44f/8/

[justinbmeyer]

@isadovskiy yeah, that first fiddle should work. I'm guessing it does in older versions? I think 2.2 has a bug around leaking (not in terms of memory) can.__read calls.

[isadovskiy]

Yes, it worked with 2.0.5 and stopped working after upgrade to 2.1.2

[justinbmeyer]

Here's a smaller version of the first example: http://jsfiddle.net/jd44f/9/