I'm still using the old angularMeteorObject in my code because of it's auto-diffing for save. I'm having an issue with it overwriting my usaved changes when an object is updated elsewhere
Sometimes in my application I want to "touch" the item, simply modifying it's "updatedAt" date. Sometimes I do this before saving the current object. Unfortunately, if I change the updatedAt date, the change is published and angularMeteor discards all my working changes, and puts in the old copy with the new updatedAt time. Is there a way I can make meteorObject ignore updates from the subscription that conflict with unsaved data?
Hello,
I'm still using the old angularMeteorObject in my code because of it's auto-diffing for save. I'm having an issue with it overwriting my usaved changes when an object is updated elsewhere
Sometimes in my application I want to "touch" the item, simply modifying it's "updatedAt" date. Sometimes I do this before saving the current object. Unfortunately, if I change the updatedAt date, the change is published and angularMeteor discards all my working changes, and puts in the old copy with the new updatedAt time. Is there a way I can make meteorObject ignore updates from the subscription that conflict with unsaved data?