squizlabs/PHP_CodeSniffer is dead, long live PHPCSStandards/PHP_CodeSniffer!
Also, please consider sponsoring the project to safeguard its continuation, as without funding, we'll have the same problem again sooner rather than later.
I'm proud to announce that as of today - the day of the first PHP 8.3-RC release - WordPress is beta compatible with PHP 8.3.
What that means is: everything we could find between static analysis and the tests has been fixed and all CI tasks pass on PHP 8.3 and CI is no longer allowed to fail on PHP 8.3.
No doubt there may still be some things which need fixing. If you find something, please report it.
This is an important release which makes significant changes to improve the accuracy, performance, stability and maintainability of all sniffs, as well as making WordPressCS much better at handling modern PHP.
Please carefully read the changelog and upgrade guides before updating!
What the f*ck people ?
Copying code I wrote into your own project and then reporting bugs which don't exist in the original project and expect me to solve your shit ????
Seriously, use Composer like a normal person and don't rip off other people's code....
And yes, they are violating the project license as well.
Coding standards lovers: if I'd be writing some sniffs to check phpDoc tags.... which tags should be taken into account and what would you want checked ?
PSR-19 would be first on my list, but I've got plenty more ideas and have created tag lists for PHPUnit, PHPStan, Psalm and a few more.
Are there more popular tools with custom annotations I should look at ?
Anything specific you'd really like to be able to enforce via #PHPCS ?
Just released: PHPUnit Polyfills 1.1.0, which syncs with PHPUnit 9.6.11 and polyfills the backports of the assertObjectHasProperty() and assertObjectNotHasProperty() methods.
If your project is still limited to PHPUnit < 10, this upgrade allows you to get rid of the deprecation notices about the assertObjectHasAttribute() and assertObjectNotHasAttribute() methods.
If you are already using the PHPUnit Polyfills 2.0.0, you're good and can ignore this message.
These versions provide compatibility hotfixes to continue to allow for running tests using a PHPUnit PHAR file after today's PHPUnit 8.5.38, 9.6.19 and 10.5.17 releases.
Accidentally wrote five sniffs to scratch my own itch over the weekend...
Not ready for public use yet (rough drafts), but working for my immediate purpose for now... (auto-fixing things to update a test suite for PHPUnit 11). 😁
Watch this space as these will enter the public domain at some point in the future...
"You're not objective as you will benefit from funds collected"...
Seriously ? I've been contributing to the project for over 8 years without getting a penny.
I could have just let the project die, but I recognized that a LOT of people depend on it (which includes me), and decided to step up, even though I'm strapped for time as it is.
I'm hoping to get most of the syntax support for PHP 8.3 ready over the next few days, which means that if all goes well, it will be included in #PHP_CodeSniffer 3.9.0 release.
The PR to add Tokenizer support for PHP 8.3 readonly anonymous classes to PHPCS is already open.