Date comparison always yields a patch about json-patch

[jrogelstad]

I did a little investigation into various deep copy methods, as I'm sure you have as well, and my conclusion was that the more important it is for the copy to be "correct" the greater the overhead involved to implement it. For example here's a pretty involved algorithm to do deep copy:

http://oranlooney.com/static/javascript/deepCopy.js
...that is described here:
http://oranlooney.com/deep-copy-javascript/

I didn't run any tests, but just looking at it I'm sure it will slow the generator down substantially, which kind of defeats the main stated benefit of this project over others. For my project I just implemented a simple work around that converts all dates to JSON strings before the object ever gets to the observer/generator:

https://github.com/xtuple/xtuple/blob/master/lib/backbone-x/source/model.js#L331
https://github.com/xtuple/xtuple/blob/master/lib/backbone-x/source/model_mixin.js#L238

If I stumble upon a better idea I will circle back on this.

Best,

John

[warpech]

I tried to fix it in the shimmed version, but I abandoned it because it won't run in the native (Object.observe) version anyway.

Reason: Object.observe can't detect changes in the Date object (tested in Chrome 28 and Chrome 30 Canary) - http://jsfiddle.net/ytz93/

[Starcounter-Jack]

As Date is not a value type and as we want to be compatible with Ecmascript Next Object.observe, I'm now closing this. I'll reopen the issue if anyone can provide some compelling new insight on the subject.

[Toub]

So, how do we generate patches for dates?
Maybe that custom comparison function could help: #92