ipfs-http-client method arguments and return types are any

[dapplion]

Curent

All ipfs methods arguments and return types are any. See below example for add

Expect

Arguments and return values to be types properly

---

"ipfs-http-client": "^48.1.2",
"typescript": "^3.8.0",
Visual Studio Code: October 2020 (version 1.51)

[achingbrain]

Please can you try with the latest RC? The core-api is now fully entyped in the ipfs-core-types module and ipfs-http-client now implements that API:

$ npm install ipfs-http-client@next

[dapplion]

Now has some types but first argument is still any.

With this version installed

  "name": "ipfs-http-client",
  "version": "49.0.5-rc.3+1823375a"

Hey you could try this new project called Typescript, it has a solid type system with good tooling and community.

[achingbrain]

Now has some types but first argument is still any.

Hmm, weird that it's picked up some of the types but not everything.

Hey you could try this new project called Typescript, it has a solid type system with good tooling and community.

I appreciate that you feel frustration over this issue but this sort of comment is not massively helpful.

[dapplion]

I appreciate that you feel frustration over this issue but this sort of comment is not massively helpful.

I'm sorry to be perceived as negative but I do feel the frustration over the quality of the types in all of protocol lab's JS libs, from IPFS, to libp2p, to utils. I know I'm beating a dead horse now, but I do want to see the JS side succeed. I really wish you could see the return on investment on such a move.

[lidel]

Should be fixed soon as part of #2945
Closing to decrease noise.