Closed elricli closed 4 years ago
Looking at your screenshot, this might be similar to the issue I was having in: https://github.com/ikappas/vscode-phpcs/issues/128
If you have basepath in your phpcs.xml file, try removing it and see if that provides the expected output from the plugin: <arg name="basepath" value="./"/>
Looking at your screenshot, this might be similar to the issue I was having in:
128
If you have basepath in your phpcs.xml file try removing it and see if that provides the expected out put from the plugin:
<arg name="basepath" value="./"/>
Thank you so much, I resolve it by remove <arg name="basepath" value="./"/>
Thank you @Blake-C - I had the same issue & that solved it!
Not seeing any errors either. no <arg name="basepath" value="./"/>
in my config. I used the example config from the WordPress Standards example.
I specifically instruct the extension to use the locally installed phpcs:
{
"phpcs.executablePath": "./vendor/bin/phpcs",
"phpcs.standard": "WordPress"
}
All the standards also seems to be installed:
$ ./vendor/bin/phpcs -i
The installed coding standards are PEAR, Zend, PSR2, MySource, Squiz, PSR1, PSR12, PHPCompatibility, PHPCompatibility, PHPCompatibilityParagonieRandomCompat, PHPCompatibilityParagonieSodiumCompat, PHPCompatibilityWP, WordPress, WordPress-Extra, WordPress-Docs and WordPress-Core
~This helped fix the extension for me, didn't work at all before it:
"phpcs.autoConfigSearch": false,
~
Discard that, it was one of my included rulesets that also have the basepath
arg as well 🤦♂
In vs code, phpcs cannot show error message.