|
| 1 | +[](https://packagist.org/packages/PHPCompatibility/phpcompatibility-wp) |
| 2 | +[](https://packagist.org/packages/PHPCompatibility/phpcompatibility-wp) |
| 3 | +[](https://github.com/PHPCompatibility/PHPCompatibilityWP/blob/master/LICENSE) |
| 4 | +[](https://travis-ci.org/PHPCompatibility/PHPCompatibilityWP) |
| 5 | + |
1 | 6 | # PHPCompatibilityWP |
2 | | -PHPCompatibility ruleset for WordPress projects |
| 7 | + |
| 8 | +Using the PHPCompatibilityWP standard, you can analyse the codebase of a WordPress-based project for PHP cross-version compatibility. |
| 9 | + |
| 10 | + |
| 11 | +## What's in this repo ? |
| 12 | + |
| 13 | +A PHPCompatibility ruleset for projects based on the WordPress CMS. |
| 14 | + |
| 15 | +This WordPress specific ruleset prevents false positives from the [PHPCompatibility standard](https://github.com/PHPCompatibility/PHPCompatibility) by excluding back-fills and poly-fills which are provided by WordPress. |
| 16 | + |
| 17 | + |
| 18 | +## Requirements |
| 19 | + |
| 20 | +* [PHP_CodeSniffer](https://github.com/squizlabs/PHP_CodeSniffer). |
| 21 | + * PHP 5.3+ for use with [PHP_CodeSniffer](https://github.com/squizlabs/PHP_CodeSniffer) 2.3.0+. |
| 22 | + * PHP 5.4+ for use with [PHP_CodeSniffer](https://github.com/squizlabs/PHP_CodeSniffer) 3.0.2+. |
| 23 | + |
| 24 | + Use the latest stable release of PHP_CodeSniffer for the best results. |
| 25 | + The minimum _recommended_ version of PHP_CodeSniffer is PHPCS 2.6.0. |
| 26 | +* [PHPCompatibility](https://github.com/PHPCompatibility/PHPCompatibility). |
| 27 | + |
| 28 | + |
| 29 | +## Installation instructions |
| 30 | + |
| 31 | +### Installation instructions using Composer |
| 32 | + |
| 33 | +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: |
| 34 | +```bash |
| 35 | +composer require --dev dealerdirect/phpcodesniffer-composer-installer:^0.4.3 phpcompatibility/phpcompatibility-wp:* |
| 36 | +composer install |
| 37 | +``` |
| 38 | + |
| 39 | +If you already have a Composer PHPCS plugin installed, run: |
| 40 | +```bash |
| 41 | +composer require --dev phpcompatibility/phpcompatibility-wp:* |
| 42 | +composer install |
| 43 | +``` |
| 44 | + |
| 45 | +Next, run: |
| 46 | +```bash |
| 47 | +vendor/bin/phpcs -i |
| 48 | +``` |
| 49 | +If all went well, you will now see that the PHPCompatibility and PHPCompatibilityWP standards are installed for PHP_CodeSniffer. |
| 50 | + |
| 51 | +### Installation instructions without Composer (unsupported) |
| 52 | + |
| 53 | +* Install [PHP CodeSniffer](https://github.com/squizlabs/PHP_CodeSniffer) via [your preferred method](https://github.com/squizlabs/PHP_CodeSniffer#installation). |
| 54 | + |
| 55 | + PHP CodeSniffer offers a variety of installation methods to suit your work-flow: Composer, [PEAR](http://pear.php.net/PHP_CodeSniffer), a Phar file, zipped/tarred release archives or checking the repository out using Git. |
| 56 | + |
| 57 | +* Install [PHPCompatibility](https://github.com/PHPCompatibility/PHPCompatibility) by [cloning the PHPCompatibility repository](https://github.com/PHPCompatibility/PHPCompatibility#installation-via-a-git-check-out-to-an-arbitrary-directory-method-2). |
| 58 | + |
| 59 | +* Install [PHPCompatibilityWP](https://github.com/PHPCompatibility/PHPCompatibilityWP) by cloning this repository. |
| 60 | + |
| 61 | +* Add the paths to the directories in which you placed your copies of the PHPCompatibility repo and the PHPCompatibilityWP repo to the PHP CodeSniffer configuration using the below command from the command line: |
| 62 | + ```bash |
| 63 | + phpcs --config-set installed_paths /path/to/PHPCompatibility,/path/to/PHPCompatibilityWP |
| 64 | + ``` |
| 65 | + For more information, see the PHP CodeSniffer wiki on the [`installed_paths` configuration variable](https://github.com/squizlabs/PHP_CodeSniffer/wiki/Configuration-Options#setting-the-installed-standard-paths). |
| 66 | + |
| 67 | +* Verify that the PHPCompatibility standard is registered correctly by running `phpcs -i` on the command line. PHPCompatibility should be listed as one of the available standards. |
| 68 | + |
| 69 | + |
| 70 | +## How to use |
| 71 | + |
| 72 | +Now you can use the following command to inspect your code: |
| 73 | +```bash |
| 74 | +./vendor/bin/phpcs -p . --standard=PHPCompatibilityWP |
| 75 | + |
| 76 | +# Or if you installed without using Composer: |
| 77 | +phpcs -p . --standard=PHPCompatibilityWP |
| 78 | +``` |
| 79 | + |
| 80 | +By default, you will only receive notifications about deprecated and/or removed PHP features. |
| 81 | + |
| 82 | +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. |
| 83 | + |
| 84 | +The minimum PHP requirement of the WordPress project at this time is PHP 5.2.4. If you want to enforce this, either add `--runtime-set testVersion 5.2-` to your command-line command or add `<config name="testVersion" value="5.2-"/>` to your [custom ruleset](https://github.com/PHPCompatibility/PHPCompatibility#using-a-custom-ruleset). |
| 85 | + |
| 86 | +For more detailed information about setting the `testVersion`, see the README of the generic [PHPCompatibility](https://github.com/PHPCompatibility/PHPCompatibility#sniffing-your-code-for-compatibility-with-specific-php-versions) standard. |
| 87 | + |
| 88 | + |
| 89 | +## License |
| 90 | + |
| 91 | +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 |
| 92 | + |
| 93 | + |
| 94 | +## Changelog |
| 95 | + |
| 96 | +### 1.0.0 - 2018-07-17 |
| 97 | + |
| 98 | +Initial release of the PHPCompatibilityWP ruleset. |
0 commit comments