PHP Code Sniffer VS PHP Parser

PHP Insights supports sniffs from PHP CodeSniffer and fixers from PHP CS Fixer. This allows you to add any sniff or fixer as long as it implements PHP_CodeSniffer\Sniffs\Sniff or PhpCsFixer\Fixer\FixerInterface.

I don’t know why but that link keeps reloading the page over and over. This one works for me: https://github.com/squizlabs/PHP_CodeSniffer/issues/3932

PHP_CodeSniffer is a widely-used tool for enforcing coding standards in PHP. It checks the code against a set of predefined coding standards (such as PSR-12, PSR-2, and many others) and provides reports with violations and recommendations for improvement. Documentation: You can find more information about PHP_CodeSniffer and its usage in the official documentation: PHP_CodeSniffer Repository

While you're at it, also include code-style checkers like phpcs, phpmd and/or php-cs-fixer

See https://github.com/squizlabs/PHP_CodeSniffer

If you are well-versed in programming then you might wanna take a look at PHPCompatibility. It will scan your codebase at different PHP version rulesets to point out code that needs upgrading. You will be needing PHPCS for this.

PHP code sniffer

Interesting. One of the reasons I stopped considering Rector is because of how memory, CPU, and time intensive it is for a non-trivial project. Instead I've been using Nikita's PHP Parser directly and getting much better results even though it isn't multi-threaded out of the box.

nikic/PHP-Parser uses a Bison equivalent for PHP parsing. See the grammar file https://github.com/nikic/PHP-Parser/blob/4.x/grammar/php7.y.

Maybe nikic/PHP-Parser is an alternative. If you only need to tokenizer part, PHP has an extension too.

nikic/PHP-Parser

Code parsing. Many linters and code builders use php-parser. It uses YACC (analog Bison) to build AST.

The PR in PHP-Parser is already on the way ↓ https://github.com/nikic/PHP-Parser/pull/834

I see there is the https://github.com/nikic/PHP-Parser

It's good idea. But something strange. Php was made as language which embedded to HTML. And how will it work without open and close tags? Instead of parsing and replacing source code as string you might use parser e.g https://github.com/nikic/PHP-Parser

I wish there was a more universal format for parsers, but I just don't think there enough people who know their stuff.

Take PHP, a language that a lot of people use: the tree-sitter-php extension doesn't support features added in 2019, let alone features added towards the end of 2020.

If you want an up-to-date PHP parser, there's really only one open-source parser[0] that's accurate enough to be used on PHP codebases old and new, and it's written in PHP. Then if you want to parse in a robust fashion you have to adopt a number of hacks to get everything working.

I hadn't encountered LSIF before – can GitHub be configured to use those maps?

[0] https://github.com/nikic/PHP-Parser