fix: ipfs dag export uses the CoreAPI and respects the offline flag #7753
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.
ipfs dag import/export
were directly using theIpfsNode
instead of aCoreAPI
which meant that--offline
doesn't "automatically" work unless we actually do some manual work inside of the code (i.e.cmdenv.GetNode(env)
doesn't do anything special with the offline flag).While we could add some magic there to make this problem less common we could also just move more towards the CoreAPI. This PR attempts that latter.
Note: Draft one has only fixed Export, still need to do Import.
cc @ribasushi