@phpstan, this tool is great for finding little oddities in your code you might not even notice yourself. Things like unused variables or impossible scenarios. Larastan extends it for Laravel apps to handle some of the magic involved. github.com/nunomaduro/lar…
@phpstan Laravel Pint is the next one, it's PHP CS Fixer under the hood but a little bit nicer in just it's easy to install and set up with no additional dependencies. laravel.com/docs/9.x/pint
@phpstan PHP Insights is also great, it's not one I use a lot but it's a good indicator for projects over time as the complexity grows and you want a measure of how things are. phpinsights.com
@phpstan One I've been really into lately is @rectorphp. It uses PHPStan under the hood but allows you to identify little problems or old legacy code that it can then fix/replace. getrector.org
@phpstan@rectorphp If you've enjoyed this, I also write a lot of articles around PHP and the Laravel ecosystem. I've got quite a back catalogue, some of them can really improve your development workflow. You can find them at medium.com/@SlyFireFox
• • •
Missing some Tweet in this thread? You can try to
force a refresh
So for those who wanted to know about my initial experience with @phpstorm and using @github's codespaces. Lets just say it wasn't great. Here's my run-through of the first hour or so.
@phpstorm@github Installed Jetbrains Gateway, First miss-step was Github CLI was too old a version, the error message for this was not clear at all and vaguely mentioned a socket not being available.
@phpstorm@github A quick ‘brew upgrade gh’ later… okay, I seem to not be able to get Gateway working with an IDE environment running the work on Codespaces.