Activate extension on other file types about vscode-php-sniffer HOT 7 CLOSED

Since those are PHP files, you can add this to your vscode settings to get this extension (and other PHP extensions) to work:

"files.associations": {
  "*.theme": "php",
  "*.module": "php",
  "*.profile": "php",
  "*.inc": "php",
  "*.install": "php"
}

from vscode-php-sniffer.

The file associations do not work with phpcs, because the phpcs by default only works with certain file types, if you want to scan other file types then you must add the --extensions argument to the CLI command, see https://github.com/squizlabs/PHP_CodeSniffer/wiki/Advanced-Usage#specifying-valid-file-extensions

It would be useful if there would be an additional setting that would allow you to pass in the extensions, for example: "phpSniffer.extensions": [ "engine", "inc", "install", "make", "module", "profile", "theme", "tpl.php", "test", "php", ]

from vscode-php-sniffer.

I need it too, for the moment it doesn't work for .module or .theme file in Drupal.

from vscode-php-sniffer.

Great, thanks for your help!

from vscode-php-sniffer.

@nkoporec did you find a resolution to this? I am experiencing the same problem.

from vscode-php-sniffer.

@butlerjraines no, unfortunalty, I have migrated from vscode to vim in the meantime.

from vscode-php-sniffer.

@nkoporec @butlerjraines One can add extensions argument into a ruleset xml file to do the equivalent of the --extensions argument as a work-around until this gets feature is developed into this extension:

<arg name="extensions" value="php,inc,theme,etc" />

This should work along with these settings mentioned above.

from vscode-php-sniffer.