-
Notifications
You must be signed in to change notification settings - Fork 5
Implement new cid(blob, ...)
#32
Comments
BREAKING CHANGE: the first argument is now the serialized output NOT the dag node. See ipld/interface-ipld-format#32
BREAKING CHANGE: the first argument is now the serialized output NOT the dag node. See ipld/interface-ipld-format#32
BREAKING CHANGE: the first argument is now the serialized output NOT the dag node. See ipld/interface-ipld-format#32
No need to change https://github.com/ipld/js-ipld-raw, because |
BREAKING CHANGE: the first argument is now the serialized output NOT the dag node. See ipld/interface-ipld-format#32
BREAKING CHANGE: the first argument is now the serialized output NOT the dag node. See ipld/interface-ipld-format#32
BREAKING CHANGE: the first argument is now the serialized output NOT the dag node. See ipld/interface-ipld-format#32
@vmx It looks likes bitcoin, zcash and ethereum all have issues, see ipld/js-ipld-zcash#13. Until this is resolved, perhaps
This means
|
@richardschneider Sounds like a good plan. Let's do this! |
@achingbrain I believe this is related to the perf work you have done for dag-pb. Could you confirm? |
That's how I came across it, yes - I don't have any hard numbers on the performance increase it would be though because it hasn't been a bottleneck in the profiling I've been doing - it just looked like a weird bit of code that the docs say should be able to be refactored to do less work (though in this case the docs appear to be ahead of the implementation). |
The IPLD Format spec was changed so that
util.cid()
now takes the binary blob and not the deserialized DAG Node as argument (#24).This is a breaking change and needs to be done on all existing formats. So please don't merge before PRs from all formats are approved. This way things can be merged and released in one go.
Instead of opening an issue on every repository, just let people know on this issue that you're working on it and then link to the PR.
The text was updated successfully, but these errors were encountered: