Next Chapter in PHPStan Saga

It acknowledges that a project has a set of errors that are there when PHPStan is first enabled, but won’t allow these errors in new or changed code..It tracks specific errors on specific lines throughout history, so it’s able to tell “you fixed these 5 errors, but these other 3 new errors appeared”.Analysis output after baseline filtering.Always the latest version..Because PHPStan is getting smarter and finds new issues in code all the time, immediate upgrade to a new version is not always possible..Because you want to keep the build green, you have to solve new errors first, or lower your level..You will be able to add the newly found errors to the baseline, upgrade and take advantage of the latest features immediately.Running in the cloud..Today, you have to run PHPStan on your CI server, or on your local machine..By taking advantage of the cloud and parallelization, you will be able to get even faster feedback and also save your own hardware resources..PHPStan will run at the same time as the rest of your CI build, saving you time.Reporting errors directly on GitLab/GitHub..Instead of scrolling through a long text log of your CI build, you will be able to read the errors right next to the code.Automatic pull requests with fixes..PHPStan will become a full-fledged member of your team!.Not only it finds errors in your code, it will also send you occasional pull requests with dead code removal, added missing typehints etc.All of these features are designed with composability in mind so you don’t have to use them all at once..For example running PHPStan in the cloud means that you will have to give the SaaS access to your source code.. More details

Leave a Reply