feat: add json patch generator RFC 6902 support #43
Conversation
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
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #43 +/- ##
=============================================
+ Coverage 0 100.00% +100.00%
=============================================
Files 0 7 +7
Lines 0 94 +94
Branches 0 31 +31
=============================================
+ Hits 0 94 +94 ☔ View full report in Codecov by Sentry. |
lukascivil
changed the title
lukascivil
force-pushed
the
feat/generate-json-patch
branch
from
f16ffe7 to
b699e68
Compare
lukascivil
force-pushed
the
feat/generate-json-patch
branch
from
e739c62 to
417b9e0
Compare
lukascivil
force-pushed
the
feat/generate-json-patch
branch
from
40284fa to
47166f1
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Pending:
https://datatracker.ietf.org/doc/html/rfc6902/#section-5