Skip to content
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

Invalid PHPCS sniff(s) specified in options or options file error #42

Open
pogla opened this issue Sep 23, 2020 · 2 comments
Open

Invalid PHPCS sniff(s) specified in options or options file error #42

pogla opened this issue Sep 23, 2020 · 2 comments

Comments

@pogla
Copy link

pogla commented Sep 23, 2020

Hi

I'm getting this error:

Screenshot 2020-09-23 at 12 32 07

With these settings:

Screenshot 2020-09-23 at 12 32 18

Does anyone know why the bot is complaining?

@forjoyilive
Copy link

I'm having the same thing happen with these... interesting:

Invalid PHPCS sniff(s) specified in options or options file. Those have been ignored temporarily. Please update the options so that scanning can continue as expected.

Option name: --phpcs-sniffs-exclude
Invalid sniff(s): Squiz.Commenting.FunctionComment.Missing, Squiz.Commenting.FunctionComment.ParamCommentFullStop, Squiz.Commenting.InlineComment.InvalidEndChar

@forjoyilive
Copy link

forjoyilive commented Dec 3, 2021

Here's the line I have in phpcs.yml:

PHPCS_SNIFFS_EXCLUDE: "WordPress.Files.FileName,Squiz.Commenting.FunctionComment.ParamCommentFullStop,Squiz.Commenting.FunctionComment.Missing,Squiz.Commenting.InlineComment.InvalidEndChar"

So it looks like WordPress.Files.FileName is recognized, but the others aren't. This is true even though (without these exclusions) we get Squiz.Commenting.FunctionComment.ParamCommentFullStop and others being reported on our commits.

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants