Download the PHP package brandembassy/coding-standard without Composer

Brand Embassy Coding Standard

• The PHP_CodeSniffer and cs-fixer rules to check that repositories are following the unified coding standard for Brand Embassy projects.
• The PHPStan default configuration file.
• PhpStorm code style and inspections (with Php Inspections (EA Extended) plugin) configuration files.

Standards

For full reference of enforcements, go through default-ecs.php where each sniff / fixer deviating from default set lists is briefly described.

@TODO list of important sniffs

Skippable sniffs / fixers

Skipping of sniffs / fixers in general or for particular files should be configured in the ecs.php of your project. This file should leverage the default-ecs.php as the default configuration, but it expected that you will make adjustments to fit your project needs.

Installation

You can install the Brand Embassy Coding Standard as a composer dependency to your project:

ECS

You can run ecs with this command (without performing automatic fixes):

Or with automatic fixes:

You can use the --clear-cache option to clear the cache before applying the fixers and sniffers:

PHPStan

• includes phpstan-strict-rules extension
• includes phpstan-nette extension
• includes max level configuration by default

To use default configuration include default-phpstan.neon in your project's PHPStan config:

Rector

To use default configuration require default-rector.php in your project's Rector config:

⚠️ Tests for Rector rules need to run in a separate process, because Rector and PHPStan use different versions of php-parser. See explanation here https://github.com/staabm/zf-select-strip/pull/8. Another way would be to run them in a separate testsuite, but then we run into problems with code-coverage.

PhpStorm

This project contains inspections and code style configurations for PhpStorm.

• BrandEmbassyCodeStyle.xml
• BrandEmbassyInspections.xml

Importing these configurations reduces number of errors in phpcs check before committing.

Versioning

This library follows semantic versioning, and additions to the code ruleset are only performed in major releases.

Testing

@TODO: inspiration - https://github.com/doctrine/coding-standard/tree/master/tests

If you are contributing to the Brand Embassy Coding Standard and want to test your contribution, you just need to execute PHPCS with the tests folder and ensure it matches the expected report: