broken livebinding after replace can.Map property or remove property

[pYr0x]

hi,

i have some interesting behaviour that brokes down the livebinding with mustache and can.Map

i have a simple template with deep properties

here is me {{test.firstname}} {{test.lastname}}

if i have that javascript, that livebinding brokes

foobar = new can.Map();

var obj = {
'firstname': 'hans',
'lastname': 'peter'
};

foobar.attr('test',obj);

this will shows the right.. but after a second time and an other object replace the "test" there is no livebinding anymore

var obj = {
'firstname': 'michael',
'lastname': 'grau'
};

foobar.attr('test',obj);

same procedure if i want to remove "test" with deep properties

foobar.removeAttr('test');

[justinbmeyer]

Thanks! I'm going to work on fixing this for 2.0.1. In the short term, if you do:

here is me {{#test}}{{firstname}} {{lastname}}{{/test}}

it will work

[pYr0x]

Any idea when 2.0.1 will be Release?

[justinbmeyer]

https://github.com/bitovi/canjs/issues/milestones

[colinexl]

I know this issue has been closed, but after the changes in this commit, our compute no longer works the way it did.

Here's a fiddle: http://jsfiddle.net/qYdwR/1180/

Before, we initialized an empty compute by using

can.compute()

Then after some async operations are done, it'll update the compute by calling

can.compute(new ConstructOfSomeSort())

This would then cause the Mustache view to update itself due to live-binding. However, after this commit, the Mustache doesn't update itself anymore. I dug around briefly and it looks like the "computed" function in compute.js is no longer being called after the can compute update.

I believe this issue is happening in the latest CanJS2 as well.

[justinbmeyer]

If you believe this is a bug, please open a new issue and reference this commit.