update about spine HOT 5 CLOSED

Doesn't seem like a biggie - you may want the update even even if the attributes haven't changed, say in the case that an association had been changed and the view needs to be re-rendered.

from spine.

Sure. I'm just looking for a way to minimize ajax traffic

from spine.

If that were the case, people would bind to the save event. This is unexpected behavior thats causing my UI to rerender much more than it needs to. IMO, update should only fire on real updates.

from spine.

@drewwells I agree this should still be open.

Maybe the 'update' event should fire as it does currently (the record has been updated, even if nothing has changed - useful for scenarios like @maccman mentioned)... but it seems weird if the 'change' event fires when nothing has changed.

from spine.

@adambiggs Either is fine with me, just something so I can use updateAttribute without having to guard it looking for actual changes in my model.

from spine.