Skip to content

Quiet stdout at a terminal - #55

Merged
nolindnaidoo merged 2 commits into
mainfrom
feat/cli-terminal-output
Oct 15, 2026
Merged

nolindnaidoo merged 2 commits into
mainfrom
feat/cli-terminal-output

Conversation

@nolindnaidoo

Copy link
Copy Markdown
Owner

stdout skips the JSON reports when it is a terminal; the stderr listing already covers a person. Piped or redirected output is unchanged. --values still prints at a terminal. Every string was already listed on stderr and the crate prints no path it did not receive, so nothing else changed.

Version: crate 0.4.4 (patch, JSON unchanged). Not published.

Local verification: fmt, clippy -D warnings and cargo test --locked pass (253 unit tests plus integration suites). Fresh binary at a pty prints no JSON and still prints --values; piped prints JSON.

stdout skips the JSON reports when it is a terminal, since the stderr listing already covers a person reading it. Piped or redirected output is unchanged, byte for byte. --values keeps printing at a terminal, because asking for the values is asking to see them.
A patch bump: the JSON on stdout is unchanged in shape and content. Only the terminal case, where nothing reads it, goes quiet.
@nolindnaidoo
nolindnaidoo merged commit 9621a1f into main Oct 15, 2026
32 checks passed
@nolindnaidoo
nolindnaidoo deleted the feat/cli-terminal-output branch October 15, 2026 08:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant