-
-
Notifications
You must be signed in to change notification settings - Fork 184
New issue
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
NoKeywordsException #7
Comments
Well, I think the exception message is quite obvious: Sniff You can either ignore this sniff (as described in README) or set after On Wednesday, December 23, 2015, David Neilsen [email protected]
Ondřej Mirtes |
So maybe more of a docs issue then? I just followed the "Using the standard as a whole" part. How do I add these extra requirements? |
There's no one correct setting. When adopting this standard, you should consider how your codebase currently looks and customize the settings for that. So if you currently don't require FQN after some keyword, you should ignore this sniff. Ignoring sniffs is described here. If you want to adopt this sniff and require FQN after extends/implements, it's described in the according section of the README dedicated to this sniff. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Doesn't seem to work out of the box.
I added the 2 deps to composer, added the sample ruleset, and ran the example command, then got the error below.
The text was updated successfully, but these errors were encountered: