-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
[Console] Styles do not respect stderr #15986
Comments
Is it by design that a |
…halasr) This PR was merged into the 3.3-dev branch. Discussion ---------- [Console] Ease writing to stderr using SymfonyStyle | Q | A | ------------- | --- | Branch? | master | Bug fix? | no | New feature? | yes | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | #15986 | License | MIT | Doc PR | n/a Commits ------- 5b0504c [Console] Ease writing to stderr using styles
The problem is that Styles like the SymfonyStyle do not use stderr when appropriate.
Errors and diagnostic and interactive messages that are not meant as actual ouput of the command should go to stderr. For background info see http://www.jstorimer.com/blogs/workingwithcode/7766119-when-to-use-stderr-instead-of-stdout
For this we merged #15795 to help people use the right one by default. But this will not take effect when using the styles currently, e.g. when using
askQuestion
in https://github.com/symfony/symfony/blob/2.8/src/Symfony/Component/Console/Style/SymfonyStyle.php#L330The text was updated successfully, but these errors were encountered: