We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Thanks to great https://github.com/Symplify/CodingStandard#abstract-class-should-have-prefix-abstract we check whether classes declared abstract do have Abstract prefix. But it could be nice to check also the "opposite way", ie. the classes starting with Abstract are in fact declared as abstract.
Abstract
// @TomasVotruba didn't you heard of such fixer? Maybe it already exists somewhere 🤔?
The text was updated successfully, but these errors were encountered:
I see. AFAIK such rule doesn't exists in sniff/fixer.
It should be rather sniff, right? So this code is not broken:
<?php -class AbstractClass +abstract class AbstractClass { } new AbstractClass;
Do you plan something similar verification for *Interface or *Trait naming?
*Interface
*Trait
Sorry, something went wrong.
No branches or pull requests
Thanks to great https://github.com/Symplify/CodingStandard#abstract-class-should-have-prefix-abstract we check whether classes declared abstract do have
Abstract
prefix. But it could be nice to check also the "opposite way", ie. the classes starting withAbstract
are in fact declared as abstract.// @TomasVotruba didn't you heard of such fixer? Maybe it already exists somewhere 🤔?
The text was updated successfully, but these errors were encountered: