Unable to locate phpcs about vscode-phpcs HOT 14 CLOSED

I can confirm that it is not working on OS X

from vscode-phpcs.

phpcs: Unable to locate phpcs. Please add phpcs to your global path or use composer depency manager to install it in your project locally

Still occurring on OS X.

from vscode-phpcs.

@auz1111 me too, phpcs: Unable to locate phpcs. Please add phpcs to your global path or use composer depency manager to install it in your project locally. still occurring on macOS.

OS: macOS High Serria
Version: 10.13.1 beta(17B46a)
VSCode version: 1.17.2

from vscode-phpcs.

This issue should be resolved in latest develop branch so please consider testing your use cases.

from vscode-phpcs.

cmd run as admin and type following command

pear install PHP_CodeSniffer

from vscode-phpcs.

I can't get it working in windows though.

from vscode-phpcs.

me to macOS Sierra phpcs is installed globally via composer it terminal I can get output of phpcs i.e. PATH is present in environment but still now working

from vscode-phpcs.

@auz1111 Which version of the extension are you using? The marketplace one or the development one?

from vscode-phpcs.

Also having this problem on Sierra with the marketplace extension.

from vscode-phpcs.

I just pushed some major new features in develop branch that need testing and include:

ability to set phpcs.executablePath
ability to set phpcs.showWarnings
ability to set phpcs.showSources
ability to enable phpcs.trace.server with messages or verbose option for tracing errors.
ability to set phpcs.composerJsonPath to something other that workspaceRoot/composer.json
Your feedback is very welcome!

from vscode-phpcs.

@ikappas I'm using Ubuntu 16.04 and I can confirm that I was able to go around this issue with version 1.0.0-beta.4. My use cases worked and I was able to see warnings from phpcsand fix files. I still had to set the full path to my phpcs global alias, was that what you intended?

from vscode-phpcs.

Hello @ikappas, I am very new to using VSCode, are there instructions to installing/switching to the development branch of a plug-in so that I can test?

from vscode-phpcs.

@Wrenbjor Hey, you can see some instruction on running the development branch of vscode-phpcs here in the README of this repo.

from vscode-phpcs.

I just released vscode-phpcs 1.0.0 which supports the VSCode 1.20+ and includes many enhancements most notable of which are:

1. multi root support
2. lint as you type support
3. automatic configuration search support
4. ability to set phpcs.executablePath
5. ability to set phpcs.showWarnings
6. ability to set phpcs.showSources
7. ability to set phpcs.composerJsonPath to something other that workspaceRoot/composer.json
8. ability to enable phpcs.trace.server with messages or verbose option for tracing errors.

I would like to give my thanks to all the people that helped track down issues in the previous betas and hope the new features help you get things done easier.

On that note, I am closing this issue to properly track any new issues in the new release. If you find this issue persists or any other issue please feel free to open a new ticket for v.1.0.0.

from vscode-phpcs.