[Console] Display errors even when --quiet is present #37796
Conversation
When using SymfonyStyle::error the message should be printed even when the --quiet option is used.
dbe85df to
8e4dcc5
Compare
|
I'm not sure about this change. Can this pull request be considered like a breaking change? This needs discussion. Quiet means no printing anything in the terminal but what the use case to print nothing? We need to catch errors more easily in a CI with this flag I think. Maybe someone have a good reason to keep it like before. |
|
I think quiet means suppressing normal output, but not error messages. A similar discussion ran under #15680 a few years ago. |
|
The referenced issue also come with a related PR (#15773). I don't think we need to do more than that as explained in the linked discussions. |
|
@fabpot I think you are not quite right. In my opinion, the exception is the smaller problem. I can catch an exception in the program and fix or bypass the cause. Only if I don't do that, the exception turns into an error. This should make errors more serious than exceptions. The PR #15773 prints out exceptions in quiet mode that were not caught. So you mean that if I, as a programmer, intercept and process all exceptions and discover that I cannot solve all problems, I shouldn't tell the user what went wrong and I cannot terminate the program properly? Instead, do I have to throw an exception and hope that it is not caught elsewhere and possibly ignored? |
When using SymfonyStyle::error the message should be printed even when
the --quiet option is used.