js-ipfs-api

[daviddias]

This issue focus on detailing the improvements we are committing to do for js-ipfs milestone 1.

js-ipfs-api is the IPFS HTTP-API client library used by js-ipfs cli and a ton of other applications that want to interact with an IPFS node through HTTP (mostly go-ipfs nodes). Currently, for js-ipfs we have to use a branch of js-ipfs-api since IPFS 0.3.11 and 0.4.0 versions different in how the http-api endpoints work. We want to support 0.4.0 http api spec, which is standardised on https://github.com/ipfs/http-api-spec.

You can find js-ipfs-api at https://github.com/ipfs/js-ipfs-api

TODO list:

• get Update to be compatible with IPFS 0.4.0 ipfs-inactive/js-ipfs-http-client#74 merged. It depends on go-ipfs 0.4.0 being released.
• implement remaining swarm features (Implement all of the swarm API calls ipfs-inactive/js-ipfs-http-client#252)
• increase code coverage to 100%
• feature GET implement get ipfs-inactive/js-ipfs-http-client#263
• enable circle-ci to run our tests as well
• update release process to the dignified pipeline
• create an examples folder that demonstrates how to:
  • use it with browserify
  • use it with webpack
  • link examples in the README
• ensure that every API call is well documented Finish and improve the documentation ipfs-inactive/js-ipfs-http-client#58 (note that the feat/files-api has more docs than master

[daviddias]

Updated the list with: ipfs-inactive/js-ipfs-http-client#252

[daviddias]

Just added in -> ipfs-inactive/js-ipfs-http-client#263

[daviddias]

This can be closed now. js-ipfs-api now follows interface-ipfs-core, which makes getting both impl to work together almost seamlessly