symfony / symfony/maker-bundle
Stop silencing RuntimeCommandException exceptions
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 3.4k
- Forks
- 427
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 20
Description
What is a purpose of silencing instances of RuntimeCommandException in ConsoleErrorSubscriber? This way one cannot use -vvv option for console commands to see the stack trace. Maker Bundle is a dev tool - there is no need to silence exceptions to print this exceptions in a "pretty way". In my opinion this increases a debugging difficulty curve.
I can work on that if we agree (in this case "work" = just will remove subscriber).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating ConsoleErrorSubscriber and trace how it handles RuntimeCommandException for console commands. Verify the current behavior with the -vvv option, then confirm that the finished change exposes the exception stack trace instead of silencing it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100