ahmadawais / vscode-tips-tricks Goto Github PK

Issue

When using the SaveAndRun command to automatically trigger phpcbf when saving a php file, the file path is not working due to forward slashes being omitted.

Solution

Install the "Save and Run with WSL" extension by author "rascui" and extend the SaveAndRun command with the line "wsl: true" as follows:

"saveAndRun": {
        "commands": [
            {
                "match": "\\.php$",
                "cmd": "phpcbf -q --standard='WordPress' ${file}",
                "silent": true,
                "wsl": true
            }
        ]
    },

In my VSCode workspace I have a complete WordPress setup although I have to work mostly on plugins. Below is the sample screenshot hope you understand my situation :)

My question is if I am working on nested directory where composer.json, phpcs.xml and vendor directory is located then also it loads phpcs from globally installed path. Thus plugins wise phpcs installed sniffs are not in priority. Thus I am getting sniff not found error. This is the custom sniff I have defined and was thrown error because of not loading phpcs from that particular directory. Any help on this scenerio will be much helpful and I couldn't find any hint from #50PHP: Setting VSCode for PHP + WordPress

Background:

I'm using Prettier - Code formatter extension for VSCode to auto-format my code on save.

Problem:

I'm used to writing single-line blocks in my sass files (where there's only a single property) i.e.

.some-class { background: #f00; }

Problem is the Prettier extension formats it to multi-lines i.e.

.some-class {
    background: #f00;
}

Solution:

The Prettier - Code formatter extension for VSCode doesn't have an option to edit stylesheets linting from VSCode Settings. However, there is an option to enable stylelint integration but this requires stylelint and stylelint-prettier npm modules.

Prettier by default uses standard stylelint configuration for stylesheet linting and formatting.

In order to allow single-line blocks in VSCode using Prettier - Code formatter extension, please take the following steps:

1. Enable stylelint integration by adding this in the VSCode Settings (JSON): "prettier.stylelintIntegration": true
2. Install stylelint and stylelint-prettier npm modules in your project directory. npm install stylelint, stylelint-prettier --save-dev
3. Add a .stylelintrc.json file at the root of your project directory with the following code:

    {
    	"plugins": ["stylelint-prettier"],
    	"rules": {
    		"block-closing-brace-newline-after": "always-multi-line",
    		"block-closing-brace-empty-line-before": "never",
    		"block-closing-brace-space-before": "always",
    		"block-opening-brace-space-after": "always",
    		"block-opening-brace-space-before": "always",
    		"block-closing-brace-newline-before": "always-multi-line",
    		"block-opening-brace-newline-after": "always-multi-line",
    		"indentation": 4
    	}
    }

You can add/customize more stylelint rules, see the entire list of rules here.

Took me a while to understand how to configure these options, if you're starting out with stylelint, I highly recommend you read its guidelines first.

"gitlens.gitExplorer.files.layout": "auto", from VSCode-Tips-Tricks/videos/Git Integration/settings.json is no longer recognized by GitLens (Unknown Configuration Setting)

php-docblock-generator

I failed to get PHP doc generator on vscode market place and it looks like this link is even blocked

https://marketplace.visualstudio.com/items?itemName=vincentkos.php-docblock-generator

All of the settings in the lesson 24 are deprecated and but the same result can be achieved with this settings
"highlight-matching-tag.styles": { "opening": { "full": { "highlight": "rgba(165, 153, 233, 0.3)" } } }

Hello, all

Is there anyone here got his setup with Local-by-Fly & vscode (with phpcs extension ) on Windows 10 work?
Note: phpcs works fine on the terminal ( WLS, or cgwin ), and for now I'm using

  "saveAndRun": {
    "commands": [{
        "match": "\\.php$",
        "cmd": "phpcbf -q --encoding=UTF-8 --standard='WordPress' ${file}",
        "silent": true,
        "wsl": true
      },
      {
        "match": "\\.php$",
        "cmd": "phpcs -q --encoding=UTF-8 --standard='WordPress' ${file}",
        "silent": true,
        "wsl": true
      }
    ]
  }

This way I can check directly in the terminal.