-
Notifications
You must be signed in to change notification settings - Fork 410
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
Adding in --quiet
and --log-level
flags
#694
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code looks fine to me. I wonder however if --quiet
should mean that we don't emit any output at all and just use the exit code. This is what many standard tools, such as diff
, do when given -q
. I think cargo build --quiet
does this as well.
I did consider that, however I do actually want the (It's possible to achieve full silence by using So maybe this should actually be a different flag, something like Or better yet, |
Okay, I changed And I added in a new |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i think this looks good! can we add a test and some docs?
I don't mind, but the existing CLI flags (e.g. |
--quiet
and --log-level
flags
(Just a heads up that I added in |
@Pauan i'd probably create a new doc under commands about log level! https://rustwasm.github.io/wasm-pack/book/commands/index.html |
@ashleygwilliams I added in docs and unit tests. |
@ashleygwilliams Ping. |
1 similar comment
@ashleygwilliams Ping. |
This is a subtle but important change as verbose informational output is useful for debugging but may conceal important issues. (Silence is golden!) |
@ashleygwilliams This is ready for review. |
No description provided.