I use it and it seems to be the most powerful quality tool in PHP world.
However, it's not so easy to use as phpcs & phpmd.
That's the reason why I didn't put it yet in my CI : it requires a bit more of configuration.
I still use it manually sometimes, like before a major release.
I'm a small business programmer. I love solving tough problems with Python and PHP. If you like what you're seeing, you should probably follow me here on dev.to and then checkout my blog.
We're in almost the exact same situation in my workplace.
We use the built-in inspections provided by PhpStorm, plus the extended inspections plugin, plus phpmd, plus phpcs. All of these inspections run automatically and continuously in PhpStorm. And that's how we work day-to-day.
But we do use PhpStan for special circumstances (like when we upgraded our code from PHP 5.6).
If you're just getting started and already use or can adopt PhpStorm, I'd get all those other inspections running first. They will change your life.
I use it and it seems to be the most powerful quality tool in PHP world.
However, it's not so easy to use as phpcs & phpmd.
That's the reason why I didn't put it yet in my CI : it requires a bit more of configuration.
I still use it manually sometimes, like before a major release.
We're in almost the exact same situation in my workplace.
We use the built-in inspections provided by PhpStorm, plus the extended inspections plugin, plus phpmd, plus phpcs. All of these inspections run automatically and continuously in PhpStorm. And that's how we work day-to-day.
But we do use PhpStan for special circumstances (like when we upgraded our code from PHP 5.6).
If you're just getting started and already use or can adopt PhpStorm, I'd get all those other inspections running first. They will change your life.
I don't know if you saw it, but you may be interested by a series of articles about code quality in PHP that I wrote recently :
🚥 How to Ensure You Write Clean Code (1/2)
🇫🇷 Boris Jamot
Thank you all for your suggestions!