These are chat archives for canjs/canjs

May 2016
Guido Smeets
May 18 2016 08:48
I'm running into some behaviour here, and I'm wondering if this is a 2.3 change or not. Hope someone can clarify. When I call attr on my component's viewModel and pass in a can.Map as the argument, it merges the properties on the viewModel's property, instead of replacing it with my new can.Map.
  1. is this intentional?
  2. is this new 2.3 behaviour or did I completely miss that this was going on in 2.2 as well?
I think it’s always been like that
you can pass true as the second argument to remove the other properties