Ancestors

Written by Alanna on 2025-01-21 at 12:43

Any recommendations for PHP code linters or static analysis tools?

[#]php #codestyle #softwareengineering

=> More informations about this toot | More toots from kelpana@mastodon.ie

Toot

Written by Matthew Weier O'Phinney on 2025-01-21 at 16:18

@kelpana I'm partial to @psalm for static analysis, though @phpstan is arguably more popular; in particular, I like that any given warning/error links you to an explanation of what causes that category of error, along with common approaches to resolving it.

I use @phpcs for code style enforcement;fixing; if you need just pure linting, php -l does that for you, and as of 8.2 or 8.3, will do multiple files/trees for you.

=> More informations about this toot | More toots from mwop@phpc.social

Descendants

Written by Juliette on 2025-01-21 at 18:00

@mwop @kelpana Happy to see @phpcs being mentioned in that list ;-)

And if you are also looking for a pure PHP linting tool which can process your whole repo in one go and works PHP cross-version, I'd suggest having a look at https://github.com/php-parallel-lint/PHP-Parallel-Lint

=> More informations about this toot | More toots from jrf_nl@phpc.social