A ruleset for PHP_CodeSniffer to check for PHP cross-version compatibility issues in projects, while accounting for polyfills provided by WordPress.
Using PHPCompatibilityWP, you can analyse the codebase of a WordPress-based project for PHP cross-version compatibility.
A ruleset for PHP_CodeSniffer to check for PHP cross-version compatibility issues in projects based on the WordPress CMS.
This WordPress specific ruleset prevents false positives from the PHPCompatibility standard by excluding back-fills and poly-fills which are provided by WordPress.
Use the latest stable release of PHP_CodeSniffer for the best results. The minimum recommended version of PHP_CodeSniffer is version 2.6.0.
The only supported installation method is via Composer.
If you don't have a Composer plugin installed to manage the
installed_paths setting for PHP_CodeSniffer, run the following from the command-line:
composer require --dev dealerdirect/phpcodesniffer-composer-installer:"^0.7" phpcompatibility/phpcompatibility-wp:"*" composer install
If you already have a Composer PHP_CodeSniffer plugin installed, run:
composer require --dev phpcompatibility/phpcompatibility-wp:"*" composer install
If all went well, you will now see that the
PHPCompatibilityWP and some more PHPCompatibility standards are installed for PHP_CodeSniffer.
Now you can use the following command to inspect your code:
./vendor/bin/phpcs -p . --standard=PHPCompatibilityWP
By default, you will only receive notifications about deprecated and/or removed PHP features.
To get the most out of the PHPCompatibilityWP standard, you should specify a
testVersion to check against. That will enable the checks for both deprecated/removed PHP features as well as the detection of code using new PHP features.
The minimum PHP requirement of the WordPress project up to WP 5.1 was 5.2.4. As of WP 5.2 it will be PHP 5.6.20. If you want to enforce this, either add
--runtime-set testVersion 5.6- to your command-line command or add
<config name="testVersion" value="5.6-"/> to your custom ruleset.
# For a project which should be compatible with PHP 5.6 and higher: ./vendor/bin/phpcs -p . --standard=PHPCompatibilityWP --runtime-set testVersion 5.6-
For more detailed information about setting the
testVersion, see the README of the generic PHPCompatibility standard.
./vendor/bin/phpcs -p . --standard=PHPCompatibilityWP --extensions=php --runtime-set testVersion 5.6-
All code within the PHPCompatibility organisation is released under the GNU Lesser General Public License (LGPL). For more information, visit https://www.gnu.org/copyleft/lesser.html
- The recommended version of the Composer PHPCS plugin is now
^0.7.0, which offers compatibility with Composer 2.0.
- The ruleset is now also tested against PHP 7.4 and 8.0. Note: full PHP 7.4 support is only available in combination with PHP_CodeSniffer >= 3.5.6. Note: runtime PHP 8.0 support is only available in combination with PHP_CodeSniffer >= 3.5.7, full support is expected in PHP_CodeSniffer 3.6.0.
- Ruleset: Updated for the Sodium_Compat polyfill which is included in WordPress 5.2.
- Composer: The recommended version of the Composer PHPCS plugin has been upped to
- Documentation: Updated the ruleset inline documentation and the Readme to reflect the change in minimum PHP requirements for WordPress as of WP 5.2.
- Documentation: Updated the ruleset inline documentation to include information on when each polyfill was added to/removed from WordPress.
- CI: The rulesets are now also tested against PHP 7.3. Note: full PHP 7.3 support is only available in combination with PHP_CodeSniffer 2.9.2 or 3.3.1+ due to an incompatibility within PHP_CodeSniffer itself.
- Ruleset: Updated for compatibility with PHPCompatibility 9.0+.
- Composer: Added dependency for a dedicated polyfill-based PHPCompatibility ruleset.
- CI: Added a test for the ruleset.
- Readme: Removed the installation instructions for a non-Composer based install.
Initial release of the PHPCompatibilityWP ruleset.