LockTech / LockTech/docker-client-ts
generated client cant stream responses
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 3
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
# can we have the ability to getReader instead?
```ts
const logs = await docker.containers.containerLogs(id, {
follow: true,
stdout: true,
});
```
will never resolve because 'follow' is true.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the generated containerLogs entry point and trace how the response is handled when follow is true. Reproduce the unresolved promise with the example request, then determine how the client should expose a readable stream or reader and verify that the request can consume ongoing logs without waiting for completion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, node.js, typescript
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100