You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, not really a bug but more of a lacking of how to achieve it.
We are trying to add something to IPFS with the library, using the remote part.
add is expecting a ByteString but there is no documentation of how to format that ByteString. Therefore it does not work and ask for the famous path argument (which is not even this name but error come from ipfs node anyway).
So how do we call the function add to provide the file name and also the encoding maybe?
res <- runRemote (add "blabla")
Anyway, I read the IPDS doc, still not clear to me.
This is not totally working, uploaded to ipfs node but the name is trash and therefore cannot handle any directly I assume, still the content is "okay" with "kkk" as value.
I assume I am missing something for the Haskell part, thanks for any tips there (may offer you later a documentation PR + some free examples if you wish)
The text was updated successfully, but these errors were encountered:
Hi,
First of all, not really a bug but more of a lacking of how to achieve it.
We are trying to add something to IPFS with the library, using the remote part.
add
is expecting a ByteString but there is no documentation of how to format that ByteString. Therefore it does not work and ask for the famouspath
argument (which is not even this name but error come from ipfs node anyway).So how do we call the function
add
to provide the file name and also the encoding maybe?Anyway, I read the IPDS doc, still not clear to me.
This is not totally working, uploaded to ipfs node but the name is trash and therefore cannot handle any directly I assume, still the content is "okay" with "kkk" as value.
I assume I am missing something for the Haskell part, thanks for any tips there (may offer you later a documentation PR + some free examples if you wish)
The text was updated successfully, but these errors were encountered: