4abd0c6fcf
This PR was merged into the 3.3-dev branch. Discussion ---------- [FrameworkBundle] Make use of stderr for non reliable output | Q | A | ------------- | --- | Branch? | master | Bug fix? | no | New feature? | yes | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | n/a | License | MIT | Doc PR | n/a Built-in commands should make use of the proper outputs. As a feature on master, considering that people may actually rely on stdout and the fact commands have been changed a lot since 2.7, I think it's not worth doing this change on lower branches. Please see also #20586 which adds a `SymfonyStyle::getErrorStyle()` shortcut for easily switching to stderr. Commits ------- |
||
---|---|---|
.. | ||
AbstractConfigCommand.php | ||
AssetsInstallCommand.php | ||
CacheClearCommand.php | ||
CachePoolClearCommand.php | ||
CacheWarmupCommand.php | ||
ConfigDebugCommand.php | ||
ConfigDumpReferenceCommand.php | ||
ContainerAwareCommand.php | ||
ContainerDebugCommand.php | ||
EventDispatcherDebugCommand.php | ||
RouterDebugCommand.php | ||
RouterMatchCommand.php | ||
TranslationDebugCommand.php | ||
TranslationUpdateCommand.php | ||
WorkflowDumpCommand.php | ||
XliffLintCommand.php | ||
YamlLintCommand.php |