Closed
Description
| Q | A |
|---|---|
| Bug report? | no |
| Feature request? | yes |
| BC Break report? | no |
| RFC? | no |
| Symfony version | 4.0.4 |
Steps to reproduce
- create a command e.g.
system:clear-logs - forget to call
parent::__construct(); - run
bin/console - command is not listed in the available commands
- no warning is visible (but it is reported correctly, read on)
Output:
The warning is printed correctly, but is like two screens of scrolling above. And it looked more like a Command registration issue, so there was no reason to scroll up. I discovered it by accident, after checking the DI configuration, trying manually tagging the command etc.
Idea 1: Move the command registration warnings bellow the command output. (At least for the "default" command)
Idea 2: Change the warning to exception. I think it is kind of similar to missing scalar constructor parameter, which throws an exception.
What do you think?