-
Notifications
You must be signed in to change notification settings - Fork 21
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
Added --pipe-stderr
and --pipe-stdout
flags
#822
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.
Sorry for the number of requested changes. Hopefully, they all make sense.
I will be happy to merge once these minor points are addressed.
Valid changes, done and pushed. Also, if you merge it, do you know when the next release will drop? In the meantime, we are working with the fork so no worries! |
Windows is failing too, i dont know why!
The "CI/ test (windows-latest, examples) is failing but I don't think it's related to this modifications, as I'm not using windows nor
|
It looks like the failure was sporadic. I will publish a new version before the end of the week. Thanks very much for your contribution! |
This was released in version 2.3.0. Please let me know if it doesn't work as you expect. |
Works perfect, thank you! |
We are using dylint in our project Scout and added the flags
--pipe-stderr
and--pipe-stdout
in order to manually capture the output, allowing for later processing, both from the CLI and when using the Dylint crate. We'd appreciate if you accept the change. Great work on Dylint!.