-
-
Notifications
You must be signed in to change notification settings - Fork 240
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add --quiet switch #172
Comments
I think this is more of a feature request for a --quiet switch. It's helpful for some output to happen by default because it acts as a guide for people who are still learning how the tool works. There is --verbose which gets way more chatty, so we can add --quiet which does nothing at all. This is fairly standard with things like apt-get being shushed with -y instead of asking for stdin yes/no, etc. |
This is now in progress |
Unfortunately, this had to be parked for now. Will put back in progress as soon as possible. |
This is in progress again. |
🎉 This issue has been resolved in version 3.1.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
I'm submitting a...
What is the current behavior?
Running Spectral lint with JSON output and then piping standard output to another program fails because the logging to standard output gets sent along with the JSON output and fails to parse.
For example, imagine an invalid OpenAPI document consisting only of:
Running an incredibly simple pipeline like this fails:
Because stdout looks like this:
What is the expected behavior?
Standard output with JSON output should be parseable so that
spectral
can be used in scripts.What is the motivation / use case for changing the behavior?
Using Spectral in a script. It is possible to work around this by dumping the JSON to a temp file with
-o
, but that complicates some scripts.Please tell us about your environment:
Other information
N/A
The text was updated successfully, but these errors were encountered: