Follow a Coding Standard

[szepeviktor]

composer require --dev wp-coding-standards/wpcs dealerdirect/phpcodesniffer-composer-installer
composer exec -- phpcs --standard=WordPress-Core src/ -s --exclude=WordPress.Files.FileName,WordPress.CodeAnalysis.AssignmentInCondition,Squiz.PHP.DisallowMultipleAssignments

These can be automatically fixed by phpcbf.

[JJJ]

Ok, let's give it a try.

I get ornery about WordPress's exact standards, but I know people find value in them, even if I think sometimes they make things worse than my own personal preferences & styles.

[szepeviktor]

but I know people find value in them

Who are those people? They are not industry professional who were raised by eating and drinking source code, but "particularly for those with vision difficulties" (from WPCS docs) and other slight disabilities.

So industry professionals MUST read code that targets people with disabilities.
That is very HARD to do.

[szepeviktor]

💡 FYI TAB characters work really well on typewriters.

[szepeviktor]

.. so I've disabled all those things in WPCS and created https://github.com/szepeviktor/phpcs-psr-12-neutron-hybrid-ruleset

[szepeviktor]

@JJJ After running the above commands I've realized that WPCS is not compatible with your Descriptive Programming ©️

Many things get indented the way you don't want.

[JJJ]

Guess I should invent my own style, eh? 😓

[szepeviktor]

YES!!