You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Opening random PHP files which are not formatted for PHP Sniffer always highlights tons of errors which makes it difficult to read.
Describe the solution you'd like
It would be great if there is an option which makes PHP Sniffer to only run if there is a .phpcs.xml file in the project because projects formatted for PHP Sniffer usually have the config file.
This way it's automatically disabled for all PHP files and only enabled for projects which use PHP Sniffer.
Describe alternatives you've considered
Disabling PHP Sniffer globally and creating a workspace for each project and turning it on for these workspaces.
The text was updated successfully, but these errors were encountered:
Thank you for your feedback. Any extension can be disabled on a per-workspace basis — could this not fulfil this request or is it more nuanced than that?
Is your feature request related to a problem? Please describe.
Opening random PHP files which are not formatted for PHP Sniffer always highlights tons of errors which makes it difficult to read.
Describe the solution you'd like
It would be great if there is an option which makes PHP Sniffer to only run if there is a
.phpcs.xml
file in the project because projects formatted for PHP Sniffer usually have the config file.This way it's automatically disabled for all PHP files and only enabled for projects which use PHP Sniffer.
Describe alternatives you've considered
Disabling PHP Sniffer globally and creating a workspace for each project and turning it on for these workspaces.
The text was updated successfully, but these errors were encountered: