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.
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.
@ufried is talking about sustainability in IT at #unkonf.
This really reminds me of my main motiviation to improve performance in #opensource static analysis tooling like #phpstan and #rectorphp
„We expect this changes to considerably reduce the amount of energy used in CI pipelines. So that’s my take on saving the planet and don’t waste energy.“
With @DaveLiddament & @markusstaab we have top-notch #PHPStan knowledge in da house. Ask all your hard PHPStan questions, and our experts will try their best to answer ;)
Ondrej Mirtes will be hosting a in-depth session on "Getting the Most Out of PHPStan'' at #dpc24. Don't miss this opportunity to learn about #PHPStan and improve your code quality. Check the schedule 👉 https://phpconference.nl
Am Dienstag, 12. Februar, geht es um 19 Uhr um das Thema #TYPO3 Projektübernahmen und -updates. @danielsiepmann zeigt uns, wie eine Übernahme gelingt und wie man das Projekt anschließend aktualisiert. Dabei gehts dann auch um Themen wie #CI, Linting, Testing mit @phpunit und Tools wie @phpstan oder #Rector.
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.
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.