respect-validation/docs/custom-validators.md
Michele Beltrame 896126caa5 Change isValid method visibility to public + Change validator registration
The "protected" isValid() method didn't work, threw an exception sying it needs to be "public".

Also the registration didn't work that way. I was unable to fix it but found an alternate way which works. Maybe it's not the right one but I'm indicating it here.
2026-02-11 14:04:18 +01:00

1.7 KiB

Custom validators

You can also create and use your own validators. To do this, you will need to create a validator and an exception to go with the validator.

To create a validator, you need to create a class that implements the Validator interface and is within the Validators namespace. It is convenient to just extend the Simple or Standard class. When the validator is called the logic inside the validate method will be executed. Here's how the class should look:

namespace My\Validation\Validators;

use Respect\Validation\Message\Template;
use Respect\Validation\Validators\Core\Simple;

#[Template(
    '{{subject}} is something',
    '{{subject}} is not something',
)]
final class Something extends Simple
{
    public function isValid(mixed $input): bool
    {
        // Do something here with the $input and return a boolean value
    }
}

The '{{subject}} is not something message would be used when you call the validator with the not().

All classes in Validation are created by the Factory class. If you want Validation to execute your validator (or validators) in the chain, you must overwrite the default Factory.

use Respect\Validation\ContainerRegistry;

ContainerRegistry::setContainer(
    ContainerRegistry::createContainer([
        'respect.validation.rule_factory.namespaces' => [
            'My\\Validation\\Validators',
            'Respect\\Validation\\Validators',
        ],
    ])
);
v::something(); // Try to load "My\Validation\Validators\Something" if any