Eventjet Coding Standard
PHP-CS-Fixer
Basic Usage:
Add the following .php-cs-fixer.dist.php
file to your project's root:, (*1)
in(['features', 'module', 'tests'])->exclude('tests/fixtures');
return Config::basic($finder);
```
### More strict rules:
To use the strict rules, use the `strict` method::
```php
<ruleset>
<rule ref="Eventjet"/>
<file>src</file>
<file>tests</file>
</ruleset>
More strict rules:
There is also a more strict ruleset which forces type hints and return types to be set., (*2)
This sniff can be problematic: If you implement interfaces or have your own interfaces which don't have
parameter type hints and return types set or if you are on legacy code, enforcing this sniff would lead to a BC break.
This sniff is also set to phpcs-only
, so phpcbf
won't fix errors automatically., (*3)
To use this ruleset, just use the corresponding rule name in your phpcs rule ref instead of the default one:, (*4)
<ruleset>
<rule ref="EventjetStrict"/>
<file>src</file>
<file>tests</file>
</ruleset>
Excluding sniffs:
For certain files:
To exclude a sniff for a certain set of files, reference the rule explicitly and add an exclude pattern:, (*5)
<rule ref="SlevomatCodingStandard.TypeHints.ParameterTypeHint.MissingNativeTypeHint">
<exclude-pattern>*Interface.php</exclude-pattern>
</rule>
Suppressing sniffs locally
To suppress a sniff directly in the code, use the @phpcsSuppress
annotation:, (*6)
/**
* @phpcsSuppress SlevomatCodingStandard.TypeHints.ParameterTypeHint.MissingNativeTypeHint
* @param int $bar
*/
public function foo($bar = 0): int
{
}
More info on this can be found here., (*7)
Exclude a whole sniff:
It is also possible to exclude a sniff completely:, (*8)
<ruleset>
<rule ref="Eventjet">
<exclude name="SlevomatCodingStandard.Classes.ClassConstantVisibility"/>
</rule>
<file>src</file>
<file>tests</file>
</ruleset>