-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[FrameworkBundle][TranslationUpdateCommand] Do not output positive feedback on stderr #35170
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
Conversation
Maybe not relevant for this specific command, but outputting informational messages on stderr is often quite legit: when the command produces technically useful output (compared to info messages which are useful only for human readers), then these should be split to stdout/stderr. |
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.
Why this PR?
src/Symfony/Bundle/FrameworkBundle/Command/ContainerDebugCommand.php
Outdated
Show resolved
Hide resolved
Because all other commands output this kind of things on stdout which seems better to me. Let's be consistent. |
f5e0d81
to
87212e4
Compare
Thank you @fancyweb. |
…positive feedback on stderr (fancyweb) This PR was merged into the 3.4 branch. Discussion ---------- [FrameworkBundle][TranslationUpdateCommand] Do not output positive feedback on stderr | Q | A | ------------- | --- | Branch? | 3.4 | Bug fix? | yes | New feature? | no | Deprecations? | no | Tickets | #34865 (comment) | License | MIT | Doc PR | - Outputing everything on stderr seems wrong. I'm going to check upper branches. Commits ------- 87212e4 [FrameworkBundle][TranslationUpdateCommand] Do not output positive feedback on stderr
Outputing everything on stderr seems wrong. I'm going to check upper branches.