| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
I agree that this operation is nice, but indeed I'd like to keep RFC 6902 compatibility, which means I'll need to refactor and make JsonPatch abstract... That'll be for a 2.0 version. As to the patch itself, it looks good, but I'd suggest the following changes:
|
Sorry, something went wrong.
|
Thanks! I'll make an update using your suggestions. |
Sorry, something went wrong.
Refactor AdditionOperation
|
Squashed |
Sorry, something went wrong.
|
Updated to make overwriteExisting final. Let me know what you think |
Sorry, something went wrong.
|
Excellent! Now I need to find the time to work on that project again... Right now I'm busy with json-schema-*... |
Sorry, something went wrong.
|
Thanks, I'll keep an eye out for any updates. |
Sorry, something went wrong.
…eration Add remove? operation
…son_pointer_double_slashes #807 JsonPointer double slashes validation
| Back | FazBrowse Home | New Git URL |
I'd like to extend JSON Patch and add a new "create" operation. It is exactly like "add", except it will not replace an existing value at the requested path. It will be useful in situations in where a client wants to ensure that they are not overwriting a value set by another client.
This was a suggestion from an email thread with the RFC6902 authors:
Although it deviates from the RFC, I think it would be useful for others to use, perhaps in a custom JsonPatch implementation as you mentioned in #9.
Let me know what you think!