These are chat archives for canjs/canjs

26th
Mar 2015
Matthew Phillips
@matthewp
Mar 26 2015 15:41
Anyone remember the issue to pull a component's viewModel out into the current scope?
found it: bitovi/canjs#1362
dylanrtt
@dylanrtt
Mar 26 2015 19:40
trying to upgrade to 2.2.1, I am observing weird behavior where attr-ing a value on one map is immediately triggering a change on another seemingly unrelated map, causing my app to break. I stepped back through the canjs commits and it seems to have been introduced in 116b2cd. My app is ugly and complicated so I am not sure if I can fiddle it
Matthew Phillips
@matthewp
Mar 26 2015 19:44
unrelated?
are you sure?
dylanrtt
@dylanrtt
Mar 26 2015 19:47
well it starts with setting a value on one map, then it goes down through map.js, validations.js, define.js, batch.js, event.js, control.js to my templated event handler for a different map with a different property name... seems unrelated to me. I don't know why the batch would trigger it in this case either
Matthew Phillips
@matthewp
Mar 26 2015 19:49
you don't have computes on one map that is listening to the other?
dylanrtt
@dylanrtt
Mar 26 2015 19:50
not that I know of, and if I did, I would think it would show in the call stack or something
when I use the older canjs code, that event handler never even runs in that situation
Justin Love
@JustinLove
Mar 26 2015 19:56
Using attr on a can.List to create new entires doesn't bind as I expected it to (2.1.4) .push works for my case, so just FYI http://jsbin.com/bonowi/1/edit?html,js,console,output
Matthew Phillips
@matthewp
Mar 26 2015 20:32
@dylanrtt thanks for the report, is there any way you can condense this down a little bit?
dylanrtt
@dylanrtt
Mar 26 2015 20:35
probably not anytime soon. maybe I can circle back in a few weeks on it