Warn about catch(Exception $e) { throw $e; } being a no-op ...
Open
Nobody has claimed this yet.
dead code detection
enhancement
- Dominant language
- PHP
- Stars
- 5.6k
- Forks
- 365
- Avg merge
- 1h 25m
- Merged PRs (30d)
- 6
Description
Only warn about the last catch block(s). Don't warn if they prevent subsequent catch statements from being reached.
Do that if the catch block has a single non-comment statement. Mention that the only effect is creating $e
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
The issue names no files or tests. Start by locating the catch-block analysis and its existing warning tests, then verify how later catch blocks are determined to be reachable. Done means warnings cover only the final applicable catch block or blocks with a single non-comment statement and explain that the only effect is creating $e.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100