Closed
Description
Current Situation
Unfortunately, the monkey patch applied to jsonpatch
doesn't seem to have really fixed the problem. I don't believe that we'll be able to resolve this issue and, even if we were, the library doesn't really seem to be maintained.
Proposed Actions
Instead of actually computing a diff, just use a replace
operation where the value is the new render. This will probably have a performance cost in cases where network latency dominates. The alternative though, is getting an error on occasion when JSON patch fails to generate a correct diff.