Download the PHP package pronamic/wp-coding-standards without Composer
On this page you can find all versions of the php package pronamic/wp-coding-standards. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Informations about the package wp-coding-standards
Pronamic WordPress Coding Standards
Pronamic WordPress Coding Standards for PHP_CodeSniffer.
Versions
We try to provide support for the last 3 major releases of PHP and WordPress in our projects.
PHP
8.3
8.2
8.1
https://www.php.net/supported-versions.php
WordPress
6.5
6.4
6.3
https://codex.wordpress.org/WordPress_Versions
Other
- https://make.wordpress.org/core/handbook/best-practices/browser-support/
- https://make.wordpress.org/core/handbook/references/php-compatibility-and-wordpress-versions/
PHP_CodeSniffer
https://github.com/PHPCSStandards/PHP_CodeSniffer
Arguments
https://github.com/PHPCSStandards/PHP_CodeSniffer/wiki/Usage
colors
By default use colors in output.
extensions
By default only check files with php
extension:
parallel
By default use 8
parallel processes.
https://github.com/squizlabs/PHP_CodeSniffer/issues/1732
sp
By default show sniff codes in all reports. By default show progress of the run.
Rules
PHPCompatibilityWP
https://github.com/PHPCompatibility/PHPCompatibilityWP
By default this package test PHP 8.1
and higher via the following setting:
PHPCompatibility
https://github.com/PHPCompatibility/PHPCompatibility
Required through PHPCompatibilityWP
.
WordPress
https://github.com/WordPress/WordPress-Coding-Standards
By default the minimum WordPress version to check is set to 6.3
via the following setting:
WordPressVIPMinimum
https://github.com/Automattic/VIP-Coding-Standards
WordPress-VIP-Go
https://github.com/Automattic/VIP-Coding-Standards
VariableAnalysis
https://github.com/sirbrillig/phpcs-variable-analysis
Exclusions
WordPress.Files.FileName.InvalidClassFileName
According to the WordPress PHP Coding Standards:
Class file names should be based on the class name with
class-
prepended and the underscores in the class name replaced with hyphens, for exampleWP_Error
becomes:
Source: https://make.wordpress.org/core/handbook/best-practices/coding-standards/php/#naming-conventions
This sniff will check on this naming convention:
We often use the PSR-4 autoloading mechanism and therefore deviate from it.
WordPress.Files.FileName.NotHyphenatedLowercase
According to the WordPress PHP Coding Standards:
Files should be named descriptively using lowercase letters. Hyphens should separate words.
Source: https://make.wordpress.org/core/handbook/best-practices/coding-standards/php/#naming-conventions
We often use the PSR-4 autoloading mechanism and therefore deviate from it.
Universal.Arrays.DisallowShortArraySyntax
According to the WordPress PHP Coding Standards:
Using long array syntax (
array( 1, 2, 3 )
) for declaring arrays is generally more readable than short array syntax ([ 1, 2, 3 ]
), particularly for those with vision difficulties. Additionally, it’s much more descriptive for beginners.Arrays must be declared using long array syntax.
Source: https://developer.wordpress.org/coding-standards/wordpress-coding-standards/php/#declaring-arrays
All versions of wp-coding-standards with dependencies
automattic/vipwpcs Version ^3.0
dealerdirect/phpcodesniffer-composer-installer Version ^1.0
phpcompatibility/phpcompatibility-wp Version ^2.1
sirbrillig/phpcs-variable-analysis Version ^2.11
squizlabs/php_codesniffer Version ^3.9
wp-coding-standards/wpcs Version ^3.1