stats output should be aware of piping
Open
Nobody has claimed this yet.
kind/enhancement
- Dominant language
- Go
- Stars
- 6.1k
- Forks
- 2.2k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 43
Description
The output of the stats command should be aware that it is being pipped (if it is being pipped) and not output curses commands in that case.
PS: I know this can be done with a script calling it repeatedly, but this is standard intelligence for curses programs.
Contributor guide
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
Locate the Docker CLI stats command entry point and inspect how it formats output when connected to a pipe. Reproduce the current behavior with a piped stats command, then verify that piped output contains data rather than curses commands while interactive output remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100