-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
'ipfs dag patch' #4782
Labels
kind/enhancement
A net-new feature or improvement to an existing feature
Milestone
Comments
whyrusleeping
added
the
kind/enhancement
A net-new feature or improvement to an existing feature
label
Mar 7, 2018
Personally, I'd use (something like) JSON Patch. We could even use IPLD objects as patches. > ipfs dag patch apply QmObj QmPatch1 QmPatch2...
> ipfs dag patch apply QmId < patch.json
> ipfs dag patch add QmObj /path "value"
... However, we'll need a general purpose dag encoder system to get this working properly (we currently only have a general purpose dag decoder system). |
Open
Waiting to resolve #4801 before tackling this since many of the decisions there will also apply here. |
Relevant IPLD spec: https://ipld.io/specs/patch/ |
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I recently chatted with a user who is using
ipfs object patch
to maintain a KV storage tree in ipfs. We should look into adding a patch command toipfs dag
so that users ofobject patch
can migrate.Note that this isnt quite as simple to implement as
ipfs object patch
is, but should still be doable under certain constraints.The text was updated successfully, but these errors were encountered: