This is a set of tools to aid developers of sniffs for PHP CodeSniffer.
Run the following from the root of your project:
composer require --dev phpcsstandards/phpcsdevtools:^1.0If you work on several different sniff repos, you may want to install this toolset globally:
composer global require --dev phpcsstandards/phpcsdevtools:^1.0Composer will automatically install dependencies and register the PHPCSDebug standard with PHP_CodeSniffer using the DealerDirect Composer PHPCS plugin.
- Install PHP CodeSniffer via your preferred method.
- Register the path to PHPCS in your system
$PATHenvironment variable to make thephpcscommand available from anywhere in your file system. - Download the latest PHPCSDevTools release and unzip/untar it into an arbitrary directory. You can also choose to clone this repository using git.
- Add the path to the directory in which you placed your copy of the PHPCSDevTools repo to the PHP CodeSniffer configuration using the below command:
phpcs --config-set installed_paths /path/to/PHPCSDevTools
⚠️ Warning: Theinstalled_pathscommand overwrites any previously setinstalled_paths. If you have previously setinstalled_pathsfor other external standards, runphpcs --config-showfirst and then run theinstalled_pathscommand with all the paths you need separated by comma's, i.e.:phpcs --config-set installed_paths /path/1,/path/2,/path/3
You can now check whether each and every sniff in your standard is accompanied by a documentation XML file (warning) as well as unit test files (error).
To use the tool, run it from the root of your standards repo like so:
# When installed as a project dependency:
vendor/bin/phpcs-check-feature-completeness
# When installed globally with Composer:
phpcs-check-feature-completeness
# When installed as a git clone or otherwise:
php -f "path/to/PHPCSDevTools/bin/phpcs-check-feature-completeness"If all is good, you will see a All # sniffs are accompanied by unit tests and documentation. message.
If there are files missing, you will see errors/warnings for each missing file, like so:
WARNING: Documentation missing for path/to/project/StandardName/Sniffs/Category/SniffNameSniff.php.
ERROR: Unit tests missing for path/to/project/StandardName/Sniffs/Category/SniffNameSniff.php.
For the fastest results, it is recommended to pass the name of the subdirectory where your standard is located to the script, like so:
phpcs-check-feature-completeness ./StandardNamedirectories One or more specific directories to examine.
Defaults to the directory from which the script is run.
-q, --quiet Turn off warnings for missing documentation.
--exclude Comma-delimited list of (relative) directories to exclude
from the scan.
Defaults to excluding the /vendor/ directory.
--no-progress Disable progress in console output.
--colors Enable colors in console output.
(disables auto detection of color support)
--no-colors Disable colors in console output.
-v Verbose mode.
-h, --help Print this help.
-V, --version Display the current version of this script.
Once this project is installed, you will see a new PHPCSDebug ruleset in the list of installed standards when you run phpcs -i.
For now, this standard only contains one sniff: PHPCSDebug.Debug.TokenList.
This sniff will display compact, but detailed information about the tokens found in a (test case) file.
This sniff is compatible with PHPCS 3.0.2+.
Typical usage:
- Set up a test case file for a new sniff you intend to write.
- Run PHPCS over the test case file using this standard to see a list of the tokens found in the file:
phpcs ./SniffNameUnitTest.inc --standard=PHPCSDebug- Or use it together with the new sniff you are developing:
phpcs ./SniffNameUnitTest.inc --standard=YourStandard,PHPCSDebug --sniffs=YourStandard.Category.NewSniffName,PHPCSDebug.Debug.TokenListThe output will look something along the lines of:
Ptr :: Ln :: Col :: Cond :: Token Type :: [len]: Content
-------------------------------------------------------------------------
0 :: L1 :: C 1 :: CC 0 :: T_OPEN_TAG :: [5]: <?php
1 :: L2 :: C 1 :: CC 0 :: T_WHITESPACE :: [0]:
2 :: L3 :: C 1 :: CC 0 :: T_COMMENT :: [32]: // Boolean not operator: All OK.
3 :: L4 :: C 1 :: CC 0 :: T_IF :: [2]: if
4 :: L4 :: C 3 :: CC 0 :: T_WHITESPACE :: [1]:
5 :: L4 :: C 4 :: CC 0 :: T_OPEN_PARENTHESIS :: [1]: (
6 :: L4 :: C 5 :: CC 0 :: T_WHITESPACE :: [1]:
7 :: L4 :: C 6 :: CC 0 :: T_CONSTANT_ENCAPSED_STRING :: [4]: 'bb'
8 :: L4 :: C 10 :: CC 0 :: T_WHITESPACE :: [1]:
9 :: L4 :: C 11 :: CC 0 :: T_IS_NOT_IDENTICAL :: [3]: !==
10 :: L4 :: C 14 :: CC 0 :: T_WHITESPACE :: [1]:
11 :: L4 :: C 15 :: CC 0 :: T_CONSTANT_ENCAPSED_STRING :: [4]: 'bb'
12 :: L4 :: C 19 :: CC 0 :: T_WHITESPACE :: [1]:
13 :: L4 :: C 20 :: CC 0 :: T_CLOSE_PARENTHESIS :: [1]: )
14 :: L4 :: C 21 :: CC 0 :: T_WHITESPACE :: [1]:
15 :: L4 :: C 22 :: CC 0 :: T_OPEN_CURLY_BRACKET :: [1]: {
16 :: L4 :: C 23 :: CC 0 :: T_WHITESPACE :: [0]:
17 :: L5 :: C 1 :: CC 0 :: T_WHITESPACE :: [1]: \t
18 :: L5 :: C 2 :: CC 0 :: T_IF :: [2]: if
19 :: L5 :: C 4 :: CC 0 :: T_WHITESPACE :: [1]:
20 :: L5 :: C 5 :: CC 0 :: T_OPEN_PARENTHESIS :: [1]: (
21 :: L5 :: C 6 :: CC 0 :: T_WHITESPACE :: [0]:
PHPCS itself can also display similar information using the -vv or -vvv verbosity flags, however, when using those, you will receive a lot more information than just the token list and, while useful for debugging PHPCS itself, the additional information is mostly just noise when developing a sniff.
Contributions to this project are welcome. Clone this repository, branch off from develop, make your changes, commit them and send in a pull request.
If unsure whether the changes you are proposing would be welcome, open an issue first to discuss your proposal.
This code is released under the GNU Lesser General Public License (LGPLv3). For more information, visit http://www.gnu.org/copyleft/lesser.html