devgeniem/geniem-rules-codesniffer

Geniem Oy (WordPress) CodeSniffer Rules

1.4.0 2024-08-05 11:36 UTC

Requires

• php: >=8.0
• automattic/vipwpcs: ^3.0
• composer/installers: ^v1 || ^2
• phpcompatibility/php-compatibility: ^9.3.5
• wp-coding-standards/wpcs: ^3.0

Requires (Dev)

• ergebnis/composer-normalize: ^2.23
• phly/keep-a-changelog: ^2.4
• roave/security-advisories: dev-latest

MIT

• Contributors

• wordpress
• tooling
• standards
• phpcs

README

Geniem (WordPress) PHP_CodeSniffer Rules

A custom set of rules to check styles for a Geniem WP projects.

Extends WordPress, WordPress-Docs, WordPress-Extra, and others, but makes some convenience changes to the rules.

Adds to the mix some of our own rules:

• Geniem.ControlStructures.ElseCatchNewline
  • Make else and catch blocks to start from new line

The Geniem standard contains over 250 rules. Check them out.

Installation

composer require --dev devgeniem/geniem-rules-codesniffer
cp vendor/devgeniem/geniem-rules-codesniffer/phpcs.xml.dist-project phpcs.xml.dist

Usage

Use vendor/bin/phpcs --standard=phpcs.xml.dist web/app/ config/ to make sure you are using the phpcs command from this package.

You could add to your project composer.json file the following:

{
    "scripts": {
        "lint": "vendor/bin/phpcs --standard=phpcs.xml.dist web/app/ config/ -s --warning-severity=0",
        "lint-all": "vendor/bin/phpcs --standard=phpcs.xml.dist web/app/ config/",
        "lint-fix": "vendor/bin/phpcbf --standard=phpcs.xml.dist --basepath=. ./web/app/ ./config/"
    }
}

After that has been added to your composer.json file, you can run composer lint to check for all the errors and warnings.

Development

This project contains few helpers to make the development experience easier and faster.

These commands are available in the composer.json file, and are used composer [command]. The composer part has been omitted for brevity.

Developers

• See contributors

License

MIT