-
Notifications
You must be signed in to change notification settings - Fork 19
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
When resolving to stdout do not display status #184
Comments
It's not ideal but However, I agree we should turn automatically quiet mode in this specific context. Thanks for reporting. |
|
Is there any way to promote this option to A) show up in the For B) |
Yes, it's definitely something to improve in the user experience. We use Clap for command-line parsing, and while there are some limitations, there are workarounds to ensure that both A and B are feasible. |
@MadVikingGod with #187 merged However, I'd like to keep this issue open as I will make some changes to accept the |
Fixed in #196 (pending approval). |
Describe the bug
When the output is stdout, the status lines (example below) will break any kind of stream processing, such as passing it to
jq
.example:
To Reproduce
Steps to reproduce the behavior:
weaver registry resolve -f json | jq .
Expected behavior
The resolve output should be in the correct format, free of any status outputs.
Additional context
These statuses are nice if we are outputting to a file or if they were on stderr.
The text was updated successfully, but these errors were encountered: