I have a question for the JSON-PATCH developers and users. I have so many clients asking me why "op": "replace" returns a OPERATION_PATH_UNRESOLVABLE on not existing path. Their argument is that JSON-PATCH is used to lower the bandwith. But this need to known the resource before computing "add" or "replace" operation. (ie. send HTTP GET before computing the HTTP PATCH)
It could be reasonably efficient to only send a replace on operation and let the server add the field or replace it. (perhaps creating a new upsert operation??)
What is your opinion or your manner to solve this problem?
I have a question for the JSON-PATCH developers and users. I have so many clients asking me why
"op": "replace"
returns aOPERATION_PATH_UNRESOLVABLE
on not existing path. Their argument is that JSON-PATCH is used to lower the bandwith. But this need to known the resource before computing "add" or "replace" operation. (ie. send HTTP GET before computing the HTTP PATCH)It could be reasonably efficient to only send a replace on operation and let the server add the field or replace it. (perhaps creating a new upsert operation??)
What is your opinion or your manner to solve this problem?