You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there,
I've got an issue. I'm migrating my code from CanJS v2 and using define maps instead of can.Map.
As I see can-map-backup uses this.attr(props, true); when restoring initial value. And it removes all the protperties added during backup. But can-define-backup just assign stored properties this[prop] = props[prop]; - and it doesn't remove new props.
Is this an expected behavior or this will be fixed in near future?
BTW Will it work as a temporary solution if I will use this.update()?
The text was updated successfully, but these errors were encountered:
Hi there,
I've got an issue. I'm migrating my code from CanJS v2 and using define maps instead of can.Map.
As I see can-map-backup uses
this.attr(props, true);
when restoring initial value. And it removes all the protperties added during backup. But can-define-backup just assign stored propertiesthis[prop] = props[prop];
- and it doesn't remove new props.Is this an expected behavior or this will be fixed in near future?
BTW Will it work as a temporary solution if I will use this.update()?
The text was updated successfully, but these errors were encountered: