Add getter for the patch operations - #45
Open
mmerruko wants to merge 1 commit into
Open
Conversation
Copy link
Copy Markdown
Sorry, something went wrong.
It might be necessary in projects where an all or nothing approach to patching is not helpful and a more fine-grain approach is needed
Copy link
Copy Markdown
|
@mmerruko Use this repository: https://github.com/dogote/json-patch |
Sorry, something went wrong.
Copy link
Copy Markdown
|
is this merged? because it is not in 1.13 release now i see the release 1.13 is after this was merged is it possible to create another release? :) |
Sorry, something went wrong.
Copy link
Copy Markdown
|
+1 for having a new release created. I would like to use the change proposed in this PR. Is there any chance of a release being created in the near future? |
Sorry, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
It might be necessary in projects where an all or nothing approach
to patching is not helpful and a more fine-grain approach is needed.
This was necessary in a project where I had to use this tool and the users were interested in applying as many operations as possible and reporting the ones that couldn't be applied.