Comment 7 for bug 1521607

I've reviewed this and I have to agree with Jamie. The problem with option 2, however, is backwards compatibility. We wouldn't be able to just shut that off entirely at the moment (not until we start working on API v3). That leaves me fairly certain that we need to either implement the entirety of JSON PATCH ourselves, or introduce a library which does this for us so we don't have to do that work.

I'll leave that decision to whomever decides to take this on.