WordPress-Coding-Standards VS docker-wordpress

Is a Docker WordPress Environment focused on the development of WordPress plugins and themes, supports WP-CLI, phpMyAdmin, Xdebug and WordPress Coding Standards - WPCS.

PHP Code Sniffer helps us to achieve uniformity of code styles, we also can add other standards, like WordPress Coding Standars, some companies define their own standards etc. There are several ways to config that, but in this article, I will manage WordPress Coding Standards through Composer so we can manage these standards per project, using VS Code IDE.

WPCS's static code checks don't seem to recognize the vulnerability either, so I opened an issue: https://github.com/WordPress/WordPress-Coding-Standards/issues/2217.

Are you a new developer in general or is WordPress new for you as a developer? In my experience it's best to practise and start with little plugins. Be sure to use a code-sniffer which enforces the WordPress coding standards.

The standard here is probably wpcs (https://github.com/WordPress/WordPress-Coding-Standards) which is a set of rules for the tool phpcs (https://github.com/squizlabs/PHP_CodeSniffer)

We use WordPress Coding Standards for PHP_CodeSniffer (WPCS) which uses Squizlabs' PHP codesniffer (phpcs) and beautifier & fixer (phpcbf) under the hood to scan and format the code.

You can also save yourself some time too by making use of the WordPress ruleset for PHPCS. I've integrated this into my code editor so it evaluates my code on-the-fly.

A little while ago, I wrote about the reasons why I changed from XAMPP to Docker, back then I shortly describe my actual Docker WordPress environment. Now, I am writing about this Docker environment in more detail.