Provide response body in the HTTP API for /api/v0/files/write endopint #7403
Labels
kind/enhancement
A net-new feature or improvement to an existing feature
need/maintainers-input
Needs input from the current maintainer(s)
topic/api
Topic api
topic/MFS
Topic MFS
topic/rpc-api
Issues related to Kubo RPC API at /api/v0
Unlike /api/v0/add endpoint that produces following response body on success:
Endpoint for
/api/v0/files/write
produces no results. Which happens to be at odds with js-ipfsfiles.write
that returns{cid, size}
pair.There had being recent discussion about this mismatch between (See: ipfs/js-ipfs#3055 (comment)) HTTP-API and JS-IPFS API. While JS-IPFS could drop return value, I think it would be more useful to change HTTP-API to produce response body instead. I for one recall having to do two HTTP calls in the past to overcome this exact limitation.
The text was updated successfully, but these errors were encountered: