Skip to content

Made the code of a validation example more robust #9993

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 4 commits into from
Closed
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions validation/custom_constraint.rst
Original file line number Diff line number Diff line change
Expand Up @@ -59,11 +59,16 @@ The validator class is also simple, and only has one required method ``validate(

use Symfony\Component\Validator\Constraint;
use Symfony\Component\Validator\ConstraintValidator;
use Symfony\Component\Validator\Exception\UnexpectedTypeException;

class ContainsAlphanumericValidator extends ConstraintValidator
{
public function validate($value, Constraint $constraint)
{
if (!is_string($value) && !(is_object($value) && method_exists($value, '__toString'))) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Now that =I review this, I've got a comment :). If a constraint allows casting an object to null then it should do so for any scalar. What about changing is_string to is_scalar? I can see that it's done here for example https://github.com/symfony/symfony/blob/master/src/Symfony/Component/Validator/Constraints/EmailValidator.php#L77.

Also by convention; a constraint should not test empty value, for this a NotNull or NotBlank constraint should be used. So it misses:

if (null === $value || '' === $value) {
    return;
}

at first.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I disagree with the proposed is_scalar() change. Even the error message of the validator says: The string "{{ string }}" contains an illegal character ... so this must only work with strings, right?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've added this:

if ('' === $value) {
    return;
}

Should it contain a trim($value) call too? Thanks!

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, casting should be ok, it's about changing the representation to make it fit, then throw an exception if it's not possible. I think we should stay consistent, if we want to keep is_string that strict, then let's remove the __toString() check.

Trimming is not as it alters the given value. Fortunately this will soon be opt-in symfony/symfony#26484.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@HeahDude I made more changes according to your comments. Thanks for the reviews and for your patience 🙏

throw new UnexpectedTypeException($value, 'string');
}

if (!preg_match('/^[a-zA-Z0-9]+$/', $value, $matches)) {
// If you're using the new 2.5 validation API (you probably are!)
$this->context->buildViolation($constraint->message)
Expand Down