coding-standards | techniques applied at Splash Damage

Since your code base is not compatible with PSR-4 autoloading, a psr-4 mapping inside your composer.json's autoload section won't work, as you noticed.

I'd say you have two choices here:

First one would be to use classmap instead:

Pass by reference is for avoiding unnecessary copy when you need faster executions, and pass by a const reference is when you want to pass it fast and read-only. And pass by copy is when you want to copy the object to be able to manipulate it in the course of the execution/implementation of your function.

After opening an issue in the relevant GitHub repo, I was able to understand the answer to my question.

Short Answer: The code I was adding was incorrect. I was adding:

A couple of pointers:

• The phpcs.xml file (can also be phpcs.xml.dist and other similar variations that have a preferred order) (not ruleset.xml), should be in the root of your project code, not in the directory you installed WPCS.

• The VS Code config would then be the path (absolute or relative) to that phpcs.xml file:

  "phpcs.standard": "/path/to/project/phpcs.xml"

  or

  "phpcs.standard": "./phpcs.xml"

You'll still need to ensure that the phpcs executable you're referring to has got the WordPress standards registered.

Reference: https://marketplace.visualstudio.com/items?itemName=ikappas.phpcs

What you describe seems to be one of the following:

• a compiler bug only triggered with /Od. It would be very helpful if you can extract the structure definitions and the offending code in a minimal program that exhibits the problem for experts to investigate the problem.

• a compiler installation problem: you may be linking to a C library incompatible with your C compiler. This may cause further problems in other areas of your program. I would strongly advise you reinstall the compiler from scratch.

First of all the extension, you are trying to install you should know the purpose why it should be used and when.

From The Yii 2 Core Framework Code Style

The following code style is used for Yii 2.x core and official extensions development. If you want to pull-request code into the core, consider using it.

We aren't forcing you to use this code style for your application. Feel free to choose what suits you better.

It is only used when you are developing Yii2 not working WITH Yii2 means only if you are going to contribute to the core functionality of the framework then use this extension

If you are working on a project which is using Yii2 framework, you don't need to install this extension as the PHPCS can directly work in this case if you have it installed, all the standards that are used already are in PHPCS are not much different,

You dont need this extension, leave it, PHPCS can do the work directly.

There is no special CSS that WordPress uses: it just employs regular old CSS like any other site. That page you linked to is showing preferred syntax conventions. I just skimmed through the page and the examples of CSS syntax that they don't like were marked incorrect ... even though most would actually function just fine from what I can tell. A little misleading.

Regarding your two snippets above: those will have the same results (though in the second one you need a space after the comma: .this, .and-this{display: none;}). The first snippet referred to as human-friendly or human-readable, with extra whitespace and line breaks to make it easier for people to read and write. The second is simply minified for faster processing by computers, which removes whitespacing and line breaks.

It should be noted that this principle of minification from your example really only applies when scaled up to hundreds/thousands of lines of code and doesn't make much of a difference with less than that.

If you already installed the git-scm.com version, you can use my second favourite on top of it, Git for Windows (https://gitforwindows.org)

It will support your Git installation out of the box without messing around with environment variables and it uses Git Bash, which emulates a common Linux command line, so most git commands you will find around on the web will work for you

If you do this, you shouldn't try to run git directly from the Windows command line, but from the Git Bash command line, which will be accessible everywhere in Windows from the right click menu

First, you don't need to require PHP CodeSniffer explicitly, because wp-coding-standards/wpcs pulls it automatically.

composer.json