This repository has been archived by the owner on Feb 12, 2024. It is now read-only.
[Types] ipfs-http-server HttpApi requires JSIPFS type #3639
Assignees
Labels
need/triage
Needs initial labeling and prioritization
Comments
achingbrain
added a commit
that referenced
this issue
Apr 30, 2021
We needed to reach into ipld in order to get at the formats so we can deserialize the data. Instead, put the data as a block and then read it out using ipfs.dag.get. Slightly inefficient but better to use the public API. Fixes #3639
achingbrain
added a commit
that referenced
this issue
Apr 30, 2021
We needed to reach into ipld in order to get at the formats so we can deserialize the data. Instead, put the data as a block and then read it out using ipfs.dag.get. Slightly inefficient but better to use the public API. Fixes #3639
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Ref: ceramicnetwork/js-ceramic#1194
a418a52 introduced this beast to the
HttpApiconstructor:@typedef {IPFS & { ipld: IPLD, libp2p: libp2p }} JSIPFS. How do we expect users to get one of these things. The two places we useHttpApiin the test don't seem to have types coverage. Is a@ts-ignorejust how it has to be for now or is there an alternative that wraps up this little beasty from an existingipfsinstance?The text was updated successfully, but these errors were encountered: