@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 | View the thread | More toots from mwop@phpc.social
=> View kelpana@mastodon.ie profile | View psalm@phpc.social profile | View phpstan@phpc.social profile | View phpcs@phpc.social profile
text/geminiThis content has been proxied by September (3851b).