Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Support for
-s
/--silent
was accidentally dropped in 5998b56. I'm not actually sure what the most useful thing to do here is. The previous--silent
CLI docs sayHowever, from things like #1946 it seems clear that it's not just a matter of silencing ivy resolution, but would likely involve silencing other stuff as well.
This PR just silences everything, since it just stubs out the stdout/stderr streams, which would silence user-inserted
println
s and other things. That also doesn't seem that useful given #1946. However, the use case of #1946 seems like it could be satisfied byshow
, which redirects all stdout to stderr so that only the final value being shown goes to stdout.One option is to move
--silent
to a flag onshow
that squelches stderr, so that we can haveshow
silence all non-JSON output while still allowing the JSON output to be usedI'm not sure what we should do here. Is there some spec for
--silent
that would be useful, and if so for what?