soderlind/vscode-phpcbf

PHP Code Beautifier and Fixer for Visual Studio Code

PHP Code Beautifier and Fixer for Visual Studio Code

This extension provides the PHP Code Beautifier and Fixer (phpcbf) command for Visual Studio Code.

phpcbf is the lesser known sibling of phpcs (PHP_CodeSniffer). phpcbf will try to fix and beautify your code according to a coding standard.

Preview

right mouse-click, in context menu, select 'Format Document'. Here using the WordPress-Core standard. You can also enable formatting on save.

Requirements

phpcbf must be installed. phpcbf is installed when you install phpcs.

I recommend phpcs version 3.2.2 or later.

A quick install is using composer. After installing composer, in your workspace root, run the following command:

composer require "squizlabs/php_codesniffer=*"

Extension Settings

This extension has the following settings:

• phpcbf.enable: [ Optional | Default: true ] enable/disable this extension.
• phpcbf.executablePath: [ Required | Default: phpcbf ] Can be:
  • ${workspaceRoot}/vendor/bin/phpcbf
  • ./vendor/bin/phpcbf
  • ~/.composer/vendor/bin/phpcbf
  • phpcbf.bat
  • /usr/local/bin/phpcbf
  • etc
• phpcbf.documentFormattingProvider: [ Optional | Default: true ] Register PHP document formatting provider, right mouse-click context menu, select 'Format Document'
• phpcbf.onsave: [ Optional | Default: false ]. Format on save. "editor.formatOnSave": true will override this setting.
• phpcbf.debug: [ Optional | Default: false ]. Write phpcbf stdout to the console.
• phpcbf.standard: [ Optional | Default: null ]. The coding standard.

The default settings are

{
    "phpcbf.enable": true,
    "phpcbf.executablePath": "phpcbf",
    "phpcbf.documentFormattingProvider": true,
    "phpcbf.onsave": false,
    "phpcbf.standard": null
}

In a multi-root project, settings can be saved in .vscode/settings.json

Coding standards

null

When set to null, phpcbf will use, if it's set, the default_standard, otherwise fallback to Pear. You set the default standard using phpcs, eg:

phpcs --config-set default_standard PSR2

Available standards

By default, the following standards are available: PEAR, Zend, PSR2, MySource, Squiz and PSR1

Additional standards

If you add a standard to phpcs, it will be available for phpcbf. Some popular standards are: Drupal, WordPress, Yii2, Magento and Symfony.

Rules file

You can also point to a phpcs.xml rules file, eg: "phpcbf.standard": "/file/path/phpcs.xml"

Known Issues

None, but this is my first vscode extension, you're warned :)

Release Notes

Please see the changelog.

Credits

I learned a lot reading the code of, and borrowing code from PHP CS Fixer for Visual Studio Code.

Copyright and License

PHP Code Beautifier and Fixer for Visual Studio Code is copyright 2018 Per Soderlind

PHP Code Beautifier and Fixer for Visual Studio Code is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 2 of the License, or (at your option) any later version.

PHP Code Beautifier and Fixer for Visual Studio Code is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU Lesser General Public License along with the Extension. If not, see http://www.gnu.org/licenses/.

vscode-phpcbf's Issues

Format selection on context menu

Hello

PHPCBF in VSCode only have Format Document in context menu. But I need Format Selection.

Also ⌘K, ⌘F short code not work for this.

How can I do this?
Or Please add this features.

Thank you.

Other folder settings shouldn't bleed over

Currently, the extension loops through all of the project's folders, and attempts to find the executable in all of them. On one hand, this is a nice redundancy, but on the other, it doesn't seem like correct behavior, if you have different configurations in each folder and would rather a mistake (like you forgot to run 'composer install' in one) to error out.

phpcbf.documentFormattingProvider: false diables the extension

As far as I can tell, disabling the phpcbf.documentFormattingProvider option disables all of the other functionality, since the rest of the extension relies on the commands.executeCommand("editor.action.formatDocument") call.

phpcbf.standard doesn't allow relative paths or ${workspaceFolder}

The following inside a .code-workspace doesn't work.

{
        "phpcs.standard": "./ruleset.xml",
        "phpcbf.debug": true,
        "phpcbf.standard": "./ruleset.xml",
}

PHPCS does properly resolve the path to ruleset.xml, but unless we explicitly set the full path from / or ~/ then it fails to resolve.

If we comment it out we hoped it would automatically resolve to the ruleset in the files parent folder like the CLI but that doesn't appear to happen either.

When we comment out the phpcbf.standard line it uses the global default which has none of our custom fixes included.

Since we are trying to make a reusable environment for our team hard coded paths don't seem like a viable solution unless we enforce all team members add the folder to the same place on their drives which is insane.

I would have thought it would resolve ${workspaceFolder} in the path but that also doesn't seem to work.

I see several PR's that seem like they could maybe be vaguely related, but none seemed to really address this particular concern.

Question: should config be reloaded on commands instead of activation

In looking into examples and other repos (https://github.com/Microsoft/vscode-tslint/blob/master/tslint/extension.ts) it seems that multi-folder projects usually load configurations inside of the registered commands.

I can't tell if activation persists beyond one command execution, so I don't know that anything is saved by loading the configuration on activation, but if it is cached, than the configuration might be for the wrong folder on subsequent calls (if the next file is in another folder).

Refactoring this might be beneficial in another way, as instead of relying on window.activeTextEditor, the registerTextEditorCommand passes textEditor as an arg that can be used (at least in that one command, less sure how to handle the other commands).

Condition of using vscode-phpcbf on vscode-insiders

General Info

OS: Windows 10
Node: 10.8.0
NPM: 6.1.0
VSCode: Insiders build

Simple Description

I have read #21, and i think i should open separate issue.

So, vscode-phpcbf extension works well before 15 August 2018 and start to not working anymore after that. I did some trial and here is my conclusion:

When does it not work?

• When i set "phpcbf.standard": "phpcs.xml" or "phpcbf.standard": "./phpcs.xml"
• Even if i change the standard to a rule name, it still doesn't format on save even though i set
  "phpcbf.onsave": true and "editor.formatOnSave": true

When does it work?

(Glad, i can still use this extension)

• Since i use WordPress, my setting is set to "phpcbf.standard": "WordPress". This works, but only if i use Shift Alt F (Format document) command. Simply saving the document won't format it automatically.

Indent when saving does not work if phpcbf has nothing to indent

Hello,

i have a question regarding phpcbf. However, if I try to save while I have nothing to save, phpcbf hangs and it doesn't work at all afterwards. A message appears at the bottom right telling me that phpcbf is currently executing it but will stay there forever until I click cancel and restart Visual Studio Code. Why could this be?

onSave Not working

PHP_CodeSniffer version 3.4.2
VS Code version 1.36.1

I can format the document by using Shift+Alt+F but the onSave setting is not formatting the document.

Turned on debugging and nothing is showing in the debug console. Here are my settings:

{
  "php.suggest.basic": false,
  "php.validate.enable": false,
  "php.executablePath": "C:\\wamp64\\bin\\php\\php7.0.33\\php.exe",
  "phpcs.standard": "WordPress",
  "phpcbf.standard": "WordPress",
  "phpcbf.onsave": true,
  "phpcbf.documentFormattingProvider": true,
  "phpcs.autoConfigSearch": false,
  "phpcbf.debug": true,
  "[php]": {
    "editor.formatOnSave": true
  },
  "phpcbf.executablePath": "phpcbf.bat"
}

Any ideas?

Support for selective use of phpcbf

Do you support the use of being able to select snippets of code to beauatify with phpcbf?

PHP error

Hi Per,

I get a "PHP Warning: file_put_contents(//phpcbf-fixed.diff): failed to open stream: Permission denied in ~/.composer/vendor/squizlabs/php_codesniffer/CodeSniffer/Reporting.php on line 277"

Any idea on how to solve this?

Thanks!

phpcbf.onpaste option

Hi,

It would be nice to have an additional "phpcbf.onpaste" option to automatically format the code when it's pasted into the editor.

onWillSaveTextDocument-listener error

I've run into the following error being thrown by this extension:

[2019-09-30 18:10:03.524] [exthost] [error] onWillSaveTextDocument-listener from extension 'persoderlind.vscode-phpcbf' threw ERROR
[2019-09-30 18:10:03.524] [exthost] [error] Error: timeout
	at Timeout.define._deliverEventAsync.setTimeout [as _onTimeout] (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:475:26)
	at ontimeout (timers.js:425:11)
	at tryOnTimeout (timers.js:289:5)
	at listOnTimeout (timers.js:252:5)
	at Timer.processTimers (timers.js:212:10)

My settings.json is:

{
    "[css]": {
        "editor.defaultFormatter": "esbenp.prettier-vscode"
    },
    "[html]": {
        "editor.defaultFormatter": "vscode.html-language-features"
    },
    "[javascript]": {
        "editor.defaultFormatter": "vscode.typescript-language-features"
    },
    "[php]": {
        "editor.defaultFormatter": "persoderlind.vscode-phpcbf"
    },
    "editor.minimap.enabled": false,
    "explorer.confirmDelete": false,
    "phpcbf.debug": true,
    "phpcbf.documentFormattingProvider": true,
    "phpcbf.executablePath": "/Users/mthomas/.composer/vendor/bin/phpcbf",
    "phpcbf.onsave": true,
    "phpcbf.standard": "WordPress",
    "workbench.startupEditor": "newUntitledFile",
    "javascript.updateImportsOnFileMove.enabled": "always",
    "editor.formatOnPaste": true,
    "editor.formatOnSave": true,
    "php.validate.run": "onType",
    "php.validate.enable": true,
    "php.suggest.basic": false,
    "editor.formatOnType": true,
    "eslint.alwaysShowStatus": true,
    "eslint.autoFixOnSave": true
}

I have tried restarting and uninstalling/re-installing this extension without any luck.

executablePath broken

I'm experiencing a strange issue.

I've got a multi-root workspace with three folders related to the project. One of the folders has a vscode folder specific settings.json. Inside it, I've set the phpcbf executablePath as a relative path.
This works after changing the settings and formatting the document works fine. But when I restart vscode it can't find the exePath anymore.

I've got debug enabled and while it's working, I get the resolved absolute path logged to console: [Extension Host] PHPCBF args: /Users/josias_r/git/myproject/api/vendor/bin/phpcbf. But when it's not working anymore (after restart) the relative path is not resolved anymore: [Extension Host] PHPCBF args: myproject/api/vendor/bin/phpcbf.

I've set the exePath to ./api/vendor/bin/phpcbf

Stops working when used with git lens

Hi,

Im using phpcbf for drupal development using the drupal/coder composer library. When I turn on git lens my code is not formatted correctly (using Format Document option of vscode). When I disable git lens it works again as expected. I dont know if this is a compatibility issue with here or git lens so posting this issue on both issue queues.

My machine
Windows 10 Pro 64 bit

My vscode settings

  "phpcbf.enable": true,
  "phpcbf.executablePath": "./vendor/squizlabs/php_codesniffer/bin/phpcbf.bat",
  "phpcbf.documentFormattingProvider": true,
  "phpcbf.onsave": false,
  "phpcbf.standard": "C:\\Users\\ainsofs\\AppData\\Roaming\\Composer\\vendor\\drupal\\coder\\coder_sniffer\\Drupal",
  "[php]": {
    "editor.defaultFormatter": "persoderlind.vscode-phpcbf"
  },

Slow execution of phpcbf

which phpcs
/usr/local/bin/phpcs

which phpcbf
/usr/local/bin/phpcbf

phpcbf -i
The installed coding standards are PEAR, Zend, PSR2, MySource, Squiz, PSR1, WordPress-VIP, WordPress, WordPress-Extra, WordPress-Docs and WordPress-Core

Settings:
"phpcbf.standard": "WordPress",

ERR An unknown error occurred. Please consult the log for more details.

Hi,

I am running VS Code for MacOS 1.21.1

Extensions installed:

ESLint 1.4.7
PHP Debug 1.12.2
phpcbf 0.0.8
phpcs 1.0.5

I updated my user settings for PHPCS to

{
    "phpcs.standard": "WordPress-Core",
    "phpcs.enable": true,
    "phpcs.executablePath": "/Users/mgargano/projects/phpcs/scripts/phpcs",
    "phpcbf.executablePath": "/Users/mgargano/projects/phpcs/scripts/phpcbf",
    "phpcbf.standard": "WordPress-Core"
}

the paths are correct, see below:

When I go to run format code (right click and format document), nothing happens and I get the following message in the console (Help > Toggle Developer Tools)
An unknown error occurred. Please consult the log for more details.

When I pull up the logs I get nothing useful, see below:

Any help would be greatly appreciated....

${workspaceRoot} inside phpcbf.debug

Hello,

i'm using my own phpcs.xml, and unfortunately vscode-phpcbf doesn't find it if i don't pass the full path of it.
Because i'm working with a team, i need to use the ${workspaceRoot} variable inside the phpcbf.debug variable.

I have the following error: ERROR: the "${workspaceRoot}/phpcs.xml" coding standard is not installed.

Does Nothing!

I really want this ext to work. I tried everything.

System:
    OS: macOS Sierra 10.12.6
    CPU: x64 Intel(R) Core(TM) i7-4850HQ CPU @ 2.30GHz
    Memory: 989.34 MB / 16.00 GB
    Shell: 5.2 - /bin/zsh

 Binaries:
    Node: 10.1.0 - ~/.nvm/versions/node/v10.1.0/bin/node
    Yarn: 1.7.0 - /usr/local/bin/yarn
    npm: 6.0.1 - ~/.nvm/versions/node/v10.1.0/bin/npm
 IDE:
    VSCode: 1.23.1 - /usr/local/bin/code

I have phpcs ext installed. This is what my settings look like…

/ Setting for phpcs.
	"phpcs.executablePath": "/usr/local/bin/phpcs",
	"phpcs.standard": "WPAA",
	// Setting for phpcbf.
	"phpcbf.debug": true,
	"phpcbf.onsave": true,
	"phpcbf.standard": "WPAA",
	"phpcbf.executablePath": "/usr/local/bin/phpcbf",
	"[php]": {
		"editor.formatOnSave": false,
		"editor.formatOnPaste": false,
	},

My coding standard is WPAA, it's my custom WordPress Coding standards setup. I set it up like this and it works in the command line.

This extension does nothing. Shows nothing in the debug console. What to do?

Here's a gif demo.

Help! 🙌

Error: executablePath not found when PhpCodeSniffer installed via Composer

Current Behavior

On save, I see the following error:

Error: PHPCBF: spawn ./vendor/bin/phpcbf ENOENT. executablePath not found.

Expected Behavior

Code is beautified on save.

Project Details

VS Code Preferences

"phpcbf.executablePath": "./vendor/bin/phpcbf",
"phpcbf.onsave": true

Directory Structure

composer.json

{
    "name": "wordimpress/wp-business-reviews",
    "description": "",
    "homepage": "https://wpbusinessreviews.com",
    "type": "wordpress-plugin",
    "license": "GPL-2.0+",
    "require": {
        "composer/installers": "^1.4"
    },
    "require-dev": {
        "squizlabs/php_codesniffer": "*",
        "wp-coding-standards/wpcs": "^0.13.1"
    },
    "scripts": {
        "post-install-cmd": [
            "\"vendor/bin/phpcs\" --config-set installed_paths vendor/wp-coding-standards/wpcs"
        ],
        "post-update-cmd": [
            "\"vendor/bin/phpcs\" --config-set installed_paths vendor/wp-coding-standards/wpcs"
        ]
    }
}

Do you see anything that would cause that error?

In 0.0.8, debug fails. `TypeError: console.group is not a function`

With "phpcbf.debug": true in the project settings I get the following in the console under Output > Log (Window):

[2018-02-21 09:53:55.757] [renderer1] [error] console.group is not a function: TypeError: console.group is not a function
    at PHPCBF.getArgs (/Users/zk/.vscode/extensions/persoderlind.vscode-phpcbf-0.0.8/extension.js:73:21)
    at PHPCBF.format (/Users/zk/.vscode/extensions/persoderlind.vscode-phpcbf-0.0.8/extension.js:96:55)
    at Promise (/Users/zk/.vscode/extensions/persoderlind.vscode-phpcbf-0.0.8/extension.js:252:30)
    at Promise (<anonymous>)
    at Object.provideDocumentFormattingEdits (/Users/zk/.vscode/extensions/persoderlind.vscode-phpcbf-0.0.8/extension.js:244:28)
    at /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:629:497
    at /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:98:622
    at new n.Class.derive._oncancel (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:75:657)
    at Object.t.asWinJsPromise (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:98:585)
    at e.provideDocumentFormattingEdits (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:629:451)

This prevents the document from being written while debugging to the console is enabled. Discovered this while trying to figure out a problem with formatting for WordPress standards.

VS Code 1.20.1 (2018-02-13)
vscode-phpcbf 0.0.8

Feature Request: auto find executable and custom standard files.

We could use the logic similar to the check of fs.exists(tmpExecutablePath) to check a few reasonable default locations, so that less configuration is necessary to run the extension.

For example, a typical place for the executable to be found is ${workspaceFolder}/vendor/bin/phpcbf and we could find that if no executablePath setting is set.

Additionally, if no standard is set, we could check for the existance of phpcs.xml and phpcs.xml.dist in the workspaceFolder, as these are standard names according to phpcs documentation.

Use WSL (bash) to execute command

Hey!

Wonder if in windows it would be possible to execute phpcbf via windows subsystem for linux (bash)

As you can see, its only a matter of sending the command via

bash -c "command here"

Why?

Well, most build systems work better on WSL (is an ubuntu system on top of windows)

Visual studio code does not accept phpcbf

Hi folks,

Received this message after upgrade vscode to 1.61 (fedora) confirmed in multiple devices/projects, so seems not to be configuration issues.

If there's any new configuration flag we could miss or any advice or help, we'll be very grateful!

Thanks

add ignorePatterns configuration

https://github.com/ikappas/vscode-phpcs/search?utf8=%E2%9C%93&q=ignorePatterns&type=

executablePath in docker container

Hello,

I'm guessing if its possible to run phpcbf in vscode through a docker container (or image). I'm trying to configure phpcbf.executablePath with value below but it's not working:

"phpcbf.executablePath": "docker exec -it name_of_container /bin/sh -c '/var/www/html/vendor/bin/phpcbf \"$@\"' -- ",

Giving me this error:

PHPCBF: spawn docker exec -it name_of_container /bin/sh -c '/var/www/html/vendor/bin/phpcbf "$@"' -- ENOENT. executablePath not found.

Could anyone help me make this work?

Doesn't fire the executable

Sorry to leave a really generic "it doesn't work" bug report, but this extension doesn't do anything for me. It's not reporting errors or any messages in the Problems window. I do have phpcbf installed, and can execute it successfully on files via command line. I've tried to hardcode the path to the phpcbf executable in my user settings file, but no joy.

extension seems to ignore phpcs.xml

PHP example file:

<?php

namespace My\App;

class Foo
{
    public function getFoo()
    {
        echo 1;
    }

}

PHPCS.XML:

<?xml version="1.0"?>
<ruleset name="MyStandard">
 <rule ref="PSR2" />
 <rule ref="PSR1.Classes.ClassDeclaration.MultipleClasses">
   <severity>0</severity>
 </rule>
</ruleset>

If I run, using shell phpcs myfile.php I get, correctly:

 12 | ERROR | [x] The closing brace for the class must go on the next line after the body

Running phpcbf app/User.php, will fix my file:

FILE                                                       FIXED  REMAINING
---------------------------------------------------------------------------
/home/abottarini/Develop/homestead/quizzy/app/User.php     1      0

The same fix won't do if I run phpcbf inside my Visual Studio, while phpcs extension is underling my error line in red.

Warning in debugger tools when saving file

In my .vscode/settings.json I have

  "phpcbf.onsave": true,

Scenario: A file is already formatted (having just saved it) and I save the file again.

When I have

"[php]": {
    "editor.formatOnSave": true
  }

I get this warning in the developer tools console

When I remove it I get this warning

Formatting seems to be working correctly but I wasn't sure if maybe I had something misconfigured.

Refactor to do process with cwd and env

I was experimenting, and looking at the http://github.com/Microsoft/TSLint repo, and found that passing a config object to ('child_process').spawn() or ('child_process').exec() works well:

let folder = vscode.workspace.getWorkspaceFolder(editor.document.uri);
let folderPath = folder.uri.fsPath;
const childprocess: ChildProcess = exec(
  `./vendor/bin/phpcbf -i`,
  {
    cwd: folderPath,
    env: process.env
  },
  (error, stdout, stderr) => {
    if (error) {
      console.error(`exec error: ${error}`);
      vscode.window.showErrorMessage(`exec error: ${error}`);
      return;
    }
    if (stdout) console.log(`stdout: ${stdout}`);
    if (stderr) console.log(`stderr: ${stderr}`);
  }
);
const childprocess2: ChildProcess = spawn( `./vendor/bin/phpcbf`, ['-i'], {
  cwd: folderPath,
  env: process.env
} );

This would allow running the executablePath without normalizing it (as seen above). It might also negate any issues with finding standards that might be easier to discover locally, i.e., installed via composer into the same folder and registered with dealerdirect/phpcodesniffer-composer-installer

Not detecting WordPress runs on a custom ruleset

Hi!

The title says it all... :)

It just formats as PSR2 although I added "phpcbf.standard" : "WordPress-Extra",

Also, "phpcbf.onsave" : true, does nothing...

Thanks!

phpcbf run only by command in console, phpcbf is not run on save

Hi!
I have windows 10 x64.
When I run console command, phpcbf forks fine.
But on save, phpcbf is not run.

http://prntscr.com/l4bjrx - it is after save.
http://prntscr.com/l4bkef - it is after run command from console.

I have some settings: http://prntscr.com/l4bkxg

Can you help me?

Still not found: executablePath (when phpcs and phpcbf installed via Composer)

I've tried all the suggestions here, but none seems to work: #1

I'm on Windows 10, and am using Git Bash as the terminal, and still getting the PHPCBF: spawn phpcbf ENOENT. executablePath not found. error.

FYI - I'm also using this VS Code extension and that finds the "phpcs.executablePath": "./vendor/bin/phpcs" path with no issues at all, which is interesting: https://marketplace.visualstudio.com/items?itemName=ikappas.phpcs

Here's my .vscode/settings.json file:

{
  "settings-key": {
    "phpcs.enable": true,
    "phpcs.executablePath": "./vendor/bin/phpcs",
    "phpcs.standard": "WordPress",
    "phpcbf.enable": true,
    "phpcbf.documentFormattingProvider": true,
    "phpcbf.onsave": true,
    "phpcbf.executablePath": "./vendor/squizlabs/php_codesniffer/bin/phpcbf",
    "phpcbf.standard": "WordPress"
  }
}

Permission denied on format document

Latest PHPCS installed and working correctly (global wordpress extra).

Latest PHPCBF installed, and also set to wordpress extra.

On 'format document' in latest visual studio code these errors appear in the developer tools console. Any ideas?

`[Extension Host] PHP Warning: file_put_contents(//phpcbf-fixed.diff): failed to open stream: Permission denied in /usr/local/Cellar/php56/5.6.30_6/lib/php/PHP/CodeSniffer/Reporting.php on line 191

/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:253 [Extension Host] PHP Warning: file_put_contents(//phpcbf-fixed.diff): failed to open stream: Permission denied in /usr/local/Cellar/php56/5.6.30_6/lib/php/PHP/CodeSniffer/Reporting.php on line 277

/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:1306 ERR An unknown error occurred. Please consult the log for more details.
/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:253 [Extension Host] PHP Warning: file_put_contents(//phpcbf-fixed.diff): failed to open stream: Permission denied in /usr/local/Cellar/php56/5.6.30_6/lib/php/PHP/CodeSniffer/Reporting.php on line 191

/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:253 [Extension Host] PHP Warning: file_put_contents(//phpcbf-fixed.diff): failed to open stream: Permission denied in /usr/local/Cellar/php56/5.6.30_6/lib/php/PHP/CodeSniffer/Reporting.php on line 277

/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:1306 ERR An unknown error occurred. Please consult the log for more details.`