ipfs-shipyard / ipfs-shipyard/net-ipfs-http-client
ReadFileAsync: Only int lengths/offsets are currently supported
- Dominant language
- C#
- Stars
- 48
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
[FileSystemApi.ReadFileAsync](https://github.com/ipfs-shipyard/net-ipfs-http-client/blob/main/src/CoreApi/FileSystemApi.cs#L194) does not allow Int64 for offset and length.
This limitation can be removed, Kubo [/cat](https://docs.ipfs.tech/reference/kubo/rpc/#api-v0-cat) now supports [int64] in these fields.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start in src/CoreApi/FileSystemApi.cs at ReadFileAsync around line 194 and compare its offset and length parameters with the Kubo /cat API documentation linked in the issue. Done means the method accepts Int64 values for both fields and supports the int64 parameters documented by Kubo.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100