-
Notifications
You must be signed in to change notification settings - Fork 124
Conversation
- Path, String format path to a file to be added to IPFS | ||
- Object, with format `{ path: </foo/bar>, stream: <data> }` | ||
- Array, an [array] of objects with the above format. | ||
|
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.
there is also the option that no 1st arg is passed, a duplex stream is returned
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.
Ahh good, added
This is s great start! Thank you @nginnever :D |
|
||
- `Recursive`. Add directory paths recursively. | ||
|
||
`callback` must follow `function (err, object) {}` signature, where `err` is an error if the operation was not successful and `object` is an ndjson return with properties { Name (string), Hash (multihash) } |
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.
What is "an ndjson return"?
There is a lot of great activity and we are really close of having add, cat and get in both js-ipfs and js-ipfs-api with the same API, which is great. @noffle @nginnever, let's set this as a priority for the day, as we need ipfs cat to unlock @haadcode. What is missing
|
@nginnever is this PR still up to date? |
hey @diasdavid, no this is dated and should be closed.
|
@nginnever thank you for confirming :) |
Beginning the files documentation. I haven't added the tests yet but plan to do so after finishing the HTTP-API for JS-IPFS. There are still some things that need to be done to reach complete feature parity with go-ipfs but this is a good place to put the documentation of where js-ipfs is in comparison.
Starting the gzip compression and tar archiving for jsipfs get command as mentioned in the readme update here.