The life of a maintainer (and generally any back-end engineer) - if your existence is acknowledged, something's probably gone wrong! I feel you, @jrf_nl
Thank you to all of the package maintainers out there 💕
it allows you to put expiration on your code comments.
a comment can expire by e.g. a github, jira or youtrack issue-url. expiration dates and composer version constraints also work.
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.
One of the first things I did when I was laid off was to cancel all my FOSS donations, which made me sad, but I’m still not sure how long this period of unemployment will last, so it was the prudent thing to so.
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.
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 ?