You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 6, 2022. It is now read-only.
util.deserialize(), which is what provides results to ipld.get(cid), should return an object where the keys represent the same set of paths that can be resolved with ipld.get(cid, path). Instead, it’s currently returning a BitcoinjsBlock instance, which is very different.
The exact format of the object depends on how we resolve the open question at the end of the original post in ipld/js-ipld#141.
The text was updated successfully, but these errors were encountered:
Closing this issue — this was a misunderstanding between @vmx and I about the intended behavior. Instead, the real issue is a combination of ipld/interface-ipld-format#34 (which needs to be fixed in this resolver) and ipld/js-ipld#142 (which needs to be fixed in js-ipld).
See also ipld/js-ipld#141.
util.deserialize()
, which is what provides results toipld.get(cid)
, should return an object where the keys represent the same set of paths that can be resolved withipld.get(cid, path)
. Instead, it’s currently returning aBitcoinjsBlock
instance, which is very different.The exact format of the object depends on how we resolve the open question at the end of the original post in ipld/js-ipld#141.
The text was updated successfully, but these errors were encountered: