Repository navigation
Add PHPStan for a little sanity - Good first issue #428
Description
I wondered how we still stumble on runtime bugs like these #427 that are totally unavoidable when using static analysis.
"scripts": {
"lint:phpstan": "../../../bin/phpstan analyse --level 8 Classes"
},I would have commited that already and added it to the CI if it werent for the "195 errors" ... even level 4 reports ~100 errors so i think this package is due to become a little safer.
Activity
[-]Add PHPStan for a little sanity[/-]anikosom commentedon Sep 24, 2026
Hi! I'd like to work on this.
My plan would be to start with a small PR that adds PHPStan (config + composer script + CI step) together with a baseline for the existing errors, so CI can catch new issues right away. Then I'd fix the baselined errors in smaller follow-up PRs, grouped by error type.
Which level would you like to target, and which branch should I base this on?
Also, should I prefer PHPDoc types over native types in public methods to avoid breaking changes for classes extending them?