Commit444d03e

committed

feature#12822 [Validation] Mention the option to pass stringable objects (javiereguiluz)

This PR was merged into the 4.4 branch.Discussion----------[Validation] Mention the option to pass stringable objectsFixes#12123.Commits-------b7b52ab [Validation] Mention the option to pass stringable objects

2 parents4d42897 +b7b52ab commit444d03eCopy full SHA for 444d03e

File tree

1 file changed

-0

lines changed

validation
- custom_constraint.rst

1 file changed

-0

lines changed

`‎validation/custom_constraint.rst‎`

Lines changed: 6 additions & 0 deletions

Original file line number	Diff line number	Diff line change
@@ -85,13 +85,19 @@ The validator class is also simple, and only has one required method ``validate(
`85`	`85`	`}`
`86`	`86`
`87`	`87`	`if (!preg_match('/^[a-zA-Z0-9]+$/', $value, $matches)) {`
	`88`	`+ // the argument must be a string or an object implementing __toString()`
`88`	`89`	`$this->context->buildViolation($constraint->message)`
`89`	`90`	`->setParameter('{{ string }}', $value)`
`90`	`91`	`->addViolation();`
`91`	`92`	`}`
`92`	`93`	`}`
`93`	`94`	`}`
`94`	`95`
	`96`	`+..versionadded::4.4`
	`97`	`+`
	`98`	+ The feature to allow passing an object as the ``buildViolation()`` argument
	`99`	`+ was introduced in Symfony 4.4.`
	`100`	`+`
`95`	`101`	Inside ``validate``, you don't need to return a value. Instead, you add violations
`96`	`102`	to the validator's ``context`` property and a value will be considered valid
`97`	`103`	if it causes no violations. The ``buildViolation()`` method takes the error

0 commit comments

Comments

(0)

Movatterモバイル変換

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

Commit444d03e

File tree

1 file changed

1 file changed

`‎validation/custom_constraint.rst‎`

0 commit comments