error_mapping

~~~~~~~~~~~~~

**type**: ``array`` **default**: ``empty``

This option permitsto modify the default targetof errors.

Imagine a custom method named ``matchingCityAndZipCode`` validates whether the cityand zip code matches.

Unfortunately, thereis no"matchingCityAndZipCode" fieldin your form,

soall that Symfony candofor youis display the error on topof the form.

With customized error mapping, you cando better: make the error be mappedto the city field.

Here areto understand the leftand the right sideof the mapping:

* The left side containsproperty paths.

*If the violationis generated on apropertyor methodof aclass, its pathis simply propertyName.

*If the violationis generated on an entryof anarrayor ArrayAccessobject, theproperty pathis [indexName].

* You can construct nestedproperty paths by concatenating them, separating properties by dots,

*for example: addresses[work].matchingCityAndZipCode

*The right side contains simply the namesof fieldsin the form.

* The left sideof the error mapping also accepts a dot ., which refersto the field itself.

That means that any error addedto the fieldis addedto the given nested field instead.