it allows you to put expiration on your code comments.
a comment can expire by e.g. a github, jira or youtrack issue-url. expiration dates and composer version constraints also work.
Today I collaborated with ondrey on a fix for #phpstan which improves a previous performance fix, which caused perf regressions in a #laravel edge-case.
The new fix allows a 2-3 seconds instead of 2-3 minutes analysis in all mentioned cases.
Fixer v3.55 brings brand new ordered_attributes rule that extends our support for #PHP8 😁. There are also multiple internal improvements, as we bumped #PHPStan level to 7 and fixed several reported issues.
Upgrading existing Drupal 10 sites to PHP8.3 is a really, really, really good idea at this point in time. Luckily, the #drupal community has great tools like #phpstan to help us along.
While making my PHP packages compatible with Laravel 11 the last few weeks, I've also spent some time and added PHPStan to all of them.
The more simpler ones are already on level 9. The more complex are still on level 5 or 6. I'm still a novice when it comes to proper type documentation. Goal is to increase levels throughout the year.
While #PHPStan 1.10.60 shipped with deprecations handilng for global constants, with 1.10.62 I made sure that we only report errors depending on the used php version to improve DX.
In #PHP, a language without a compiler, static checking via #PHPStan is really neat. I'm running this on the command line ever now and then to see whether I messed something up during a rename or refactoring. That's not as convenient as a type checker in an IDE like Xcode which is constantly running in the background, but it's bridging a lot of the gaps.