Updated with ECS 12 and ECSConfig::configure()
simple way to work with configs.
When I give talks about coding standards, I ask people 2 questions: do you use coding standards? Do you write your own sniffs? On average, above 50 % uses it, but only 1-2 people wrote their own sniff.
PSR-2 is great for start, but main power is in those own sniffs. Every project has their own need, every person has different preferences.
I Google then and found outdated or complicated sources, so I've decided to write down a reference post for those, who want to start with sniffs. Let's look what will show all you need (and nothing more) to know to write your first sniff.
Are you new to PHP Coding Standard Tools? You can read intro How PHP Coding Standard Tools Actually Work to grasp the idea behind them. Or just go on if you're ready to start...
Today we'll pick an example a from my friend Martin Hujer. Once told me about sniff that checks that all exception classes have "Exception" suffix.
I said: How is it useful in practise? We all know that is common knowledge to write them this way. He replied: Well, we found some even in our code base.
The point is not in the count of fixed cases, but in CI based responsibility. From now on, people'll NEVER have to think about it and they can focus on more valuable processes that CI cannot do, like writing AliPay integration.
ExceptionNameSniff
"An exception class should have "Exception" suffix."
PHP_CodeSniffer\Sniffs\Sniff
interfaceIt covers 2 required methods:
use PHP_CodeSniffer\Sniffs\Sniff;
final class ExceptionNameSniff implements Sniff
{
/**
* @return int[]
*/
public function register(): array
{
}
public function process(File $file, $position): void
{
}
}
A register()
method returns list of tokens to subscribe to. Which token should we put there?
Note: You can find all tokens in PHP manual.
From "An exception class should have "Exception" suffix." I thought the T_CLASS
would be ideal:
public function register(): array
{
return [T_CLASS];
}
It would match this part of php code:
**class** SomeException extends Exception { # this is one line in your code
T_CLASS
would match also these false positives:
new **class**() extends Exception { # anonymous class
**class** SomeClass { # class without parent
It might be a little tricky to find out the easiest way to check the rule. Here you'd have to detect these cases and skip them as well.
What is exception in natural language description (not PHP)? A class that extends another class that has suffix "Exception".
So this would save us bit of coding and thinking:
public function register(): array
{
return [T_EXTENDS];
}
process()
MethodThis method has 2 arguments.
public function process(File $file, $position)
{
}
File $file
object holds all tokens of the file and helper methods.$position
is int for current located T_EXTENDS
token.There are 2 parts while writing a sniff:
T_EXTENDS
doesn't tell a lot.Let's take it one a by one:
A class that extends another class that has suffix "Exception".
A File
has useful findNext()
method:
$file->findNext(array ['tokens to find'], int 'where to start looking');
It returns position of token found or null, if none.
We need to find a string after T_EXTENDS
.
$parentClassNamePosition = $file->findNext([T_STRING], $position);
// File has all the tokens, so we get the one with name
$parentClassNameToken = $file->getTokens()[$parentClassNamePosition];
// and check it's Exception
if (substr($parentClassNameToken['content'], -strlen('Exception')) !== 'Exception')) {
// the parent class it not and exception
return;
}
When the code gets pass this check, we know we have exception there.
Would you what to do know? The process will be the same - to check if class name ends with "Exception" -, but instead of findNext()
method we'll use findPrevious()
:
// Get position of nearest previous string token
$classNamePosition = $file->findPrevious([T_STRING], $position);
// Get the token for it
$classNameToken = $file->getTokens()[$classNamePosition];
// Detect the content of token ends with "Exception"
if (substr($classNamePosition['content'], -strlen('Exception')) === 'Exception')) {
// the current class ends with "Exception"
return;
}
When this section passes, we know we have exception without "Exception" suffix there.
Reporting the error
The last method we will use is addFixableError()
.
In pseudo code:
$file->addFixableError(
'Infomative message about error',
'Where is the token with invalid content',
'ID of this Sniff to display in error report - class or some string'
);
In out case:
$file->addFixableError(
'An exception class should have "Exception" suffix.',
$position - 2,
self::class
);
Tada!
And extract stringEndsWith()
method to make code more readable.
use PHP_CodeSniffer\Sniffs\Sniff;
final class ExceptionNameSniff implements Sniff
{
/**
* @return int[]
*/
public function register(): array
{
return [T_EXTENDS];
}
public function process(File $file, $position): void
{
$parentClassNamePosition = $file->findNext([T_STRING], $position);
$parentClassNameToken = $file->getTokens()[$parentClassNamePosition];
// Does it ends with "Exception"?
if (! $this->stringEndsWith($parentClassNameToken['content'], 'Exception')) {
// The parent class it not and exception, neither it this
return;
}
$classNamePosition = $file->findPrevious([T_STRING], $position);
$classNameToken = $file->getTokens()[$classNamePosition];
if ($this->stringEndsWith($classNamePosition['content'], 'Exception')) {
// The current class ends with "Exception", it's ok
return;
}
$file->addFixableError('An exception class should have "Exception" suffix.', $position - 2, self::class)
}
private function stringEndsWith(string $name, string $needle): bool
{
return (substr($name, -strlen($needle)) === $needle);
}
}
You can find final Sniff on Github and use it right away of course.
With ECS register the checker class in ecs.php
:
// ecs.php
use Symplify\EasyCodingStandard\Config\ECSConfig;
use Symplify\CodingStandard\Sniffs\Naming\ExceptionNameSniff;
return ECSConfig::configure()
->withRules([
ExceptionNameSniff::class,
]);
And run:
vendor/bin/ecs check src
Congrats to your first sniffs! How do you like it?
Happy coding!
Do you learn from my contents or use open-source packages like Rector every day?
Consider supporting it on GitHub Sponsors.
I'd really appreciate it!