We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
ipld/interface-ipld-format recently had types added - the return value from multiformats/legacy should be compatible with that type.
multiformats/legacy
Right now js-IPFS expects IPLD formats to be of type https://github.com/ipfs/js-ipfs/blob/master/packages/ipfs-core-types/src/ipld/format.ts but these aren't the same as ipld/interface-ipld-format. The next js-IPFS release will expect ipld/interface-ipld-format so that's the type multiformats/legacy should return.
Refs: ipfs/js-ipfs#3586
The text was updated successfully, but these errors were encountered:
Short answer, use blockcodec-to-ipld-format instead
Sorry, something went wrong.
@achingbrain should we get rid of the /legacy export from here entirely and document the new lib since you've basically solved all that there?
/legacy
(working backward through my notifications, ignore my comment as I now see #77!)
Successfully merging a pull request may close this issue.
ipld/interface-ipld-format recently had types added - the return value from
multiformats/legacy
should be compatible with that type.Right now js-IPFS expects IPLD formats to be of type https://github.com/ipfs/js-ipfs/blob/master/packages/ipfs-core-types/src/ipld/format.ts but these aren't the same as ipld/interface-ipld-format. The next js-IPFS release will expect ipld/interface-ipld-format so that's the type
multiformats/legacy
should return.Refs: ipfs/js-ipfs#3586
The text was updated successfully, but these errors were encountered: