-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Drop Patch support #64
Comments
Yeah we have been discussing this as we are noticing patches aren't actually less data in the examples we have used. We think maybe our jsonpatch implementations aren't the most performant and could be doing things a bit smarter. We also want to run tests with large diddocs to see the comparisons.. more testing needed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I know this has been discussed elsewhere, but adding issue for clarity.
I think the complexity of patch isn't worth the benefits it brings. If each entry is just a new full DID Document, it is a much simpler solution.
The text was updated successfully, but these errors were encountered: