coreapi: replace coreiface.DagAPI with ipld.DAGService #5922
Conversation
This file contains 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
License: MIT Signed-off-by: Łukasz Magiera <magik6k@gmail.com>
magik6k
added
need/community-input
ghost
assigned
51 tasks
schomatis
approved these changes
Jan 14, 2019
Stebalien
approved these changes
Jan 21, 2019
Conceptually using go-ipld-format.DAGService is going to be closer to js/ipfs-interface-core, only the names are a bit different - |
|
SGTM. |
Stebalien
changed the title
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.
As
api.Dag()is the interface to IPLD, this feels like the right thing to do.This wasn't done this way before because we keep format parsers in a global map in
core/coredag, exposing ipld interfaces directly would make it tricky for outside code to do things like parse json to dag-cbor, but from my experience most Go code which touches IPLD doesn't really need those parsers.(Since this is mostly a yes/no decision, I'd like this to move relatively fast as it's blocking a chunk of work in go-ipfs-http-api)