-
Notifications
You must be signed in to change notification settings - Fork 298
Conversation
1f32d00
to
e4164f1
Compare
e4164f1
to
5dcc4a0
Compare
@noffle I got a:
Seems that on the interface-ipfs-core tests expect two different result types, check: |
Addressed! See ipfs-inactive/interface-js-ipfs-core#28 (comment) |
@@ -0,0 +1,125 @@ | |||
/* eslint-env mocha */ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do these tests cover something that interface-ipfs-core tests don't cover? If yes, why not have all of them at interface-ipfs-core for get?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm also getting am error from this file, which makes all the browser tests to fail:
ERROR in ./test/api/get.spec.js
Module build failed: TypeError: Cannot read property 'apply' of undefined
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I get it, these are the tests for the options supported by go-ipfs
Fixed the browser tests on https://github.com/ipfs/js-ipfs-api/tree/feat/ipfs.files.get :) |
Closed in favour of #337. |
Builds on @nginnever's work, bringing the rest of the implementation to completion.
Requires ipfs-inactive/interface-js-ipfs-core#28 to be merged first to get tests passing.