We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently warnings (preview feature, deprecated feature...) is written to stderr but those are not errors.
This behaviors can break scripts in powershell if we make them fail automatically if something is written to stderr.
Those outputs should be written to the standard output to avoid false error.
The text was updated successfully, but these errors were encountered:
thanks for reporting, this is a known issue, and there's a fix in underlying framework to fix it. @jiasli can share more detail
Sorry, something went wrong.
We have added option --only-show-errors in #12604 to disable warnings that are written to stderr. It will be included in S167 release.
--only-show-errors
stderr
jiasli
No branches or pull requests
Currently warnings (preview feature, deprecated feature...) is written to stderr but those are not errors.
This behaviors can break scripts in powershell if we make them fail automatically if something is written to stderr.
Those outputs should be written to the standard output to avoid false error.
The text was updated successfully, but these errors were encountered: