-
-
Notifications
You must be signed in to change notification settings - Fork 157
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
Validate command output is polluted by noisy messages #1095
Comments
Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request. |
Regarding silent parameter the current validate command already has a boolean flag |
This issue has been automatically marked as stale because it has not had recent activity 😴 It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation. There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model. Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here. Thank you for your patience ❤️ |
still relevant |
Yeah, output-file param will become more and more necessary as we do more UI/UX improvements. |
@Souvikns Could you please assign this issue to me? Thank you! |
Describe the bug
Validate command supports multiple diagnostics formats.
I assume that formats like json or junit are intended to be processed by machines.
However, validate command standard output is a mix of the selected diagnostics format and informational messages.
User must parse / filter standard output to end up with the expected file.
How to Reproduce
Expected behavior
It would be nice to separate command logs from actual output.
Those options could work:
The text was updated successfully, but these errors were encountered: