We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Add new "About Standards" page This new page contains more generic information about: * The difference between a project ruleset and a standard. * Requirements for a standard. * Naming conventions for sniffs.
Coding-Standard-Tutorial: update the tutorial * Remove mention of creating the standards in the PHPCS `Standards` directory and replace it with information about registering a standard with PHPCS via the `installed_paths` command. * Add note about the token array containing additional information. * Modernize the sniff code sample. - Replace the file docblock with a simpler class docblock. - Use the correct namespace for the standard. - Make it a `final` class. - Use short arrays. - Remove `//end ...` comments. - Improve type specificity in the docblocks. - Remove PHP close tag. * Improve the test code by including code samples which should *not* be flagged (but would trigger the sniff). * Use the more common term (class) "property" instead of "member variable". * Fix grammatical error. * Use fenced code blocks for bash commands. * Various other markdown tweaks for readability.
Coding-Standard-Tutorial: update code sample ... to prevent a deprecation notice on PHP 7.4 and a parse error on PHP 8.0+. Fixes PHPCSStandards/PHP_CodeSniffer#496
Fix some grammar issues and typos
Use highlighted blocks for important information Ref: https://github.com/orgs/community/discussions/16925
Update URLs to point to the PHPCSStandards repo
Updated Coding Standard Tutorial (markdown)
Be a bit more forceful about needing the category sub-directory for sniffs (ref #627)
Created Coding Standard Tutorial (markdown)