@@ -10,7 +10,7 @@ class, the metadata is defined by the class itself. When validating simple value
10
10
the metadata must be passed to the validation methods.
11
11
12
12
Class metadata can be defined in a configuration file or in the class itself.
13
- The Validator component retrieves that metadata using a set of loaders.
13
+ The Validator component collects that metadata using a set of loaders.
14
14
15
15
.. seealso ::
16
16
@@ -54,12 +54,13 @@ In this example, the validation metadata is retrieved executing the
54
54
55
55
.. tip ::
56
56
57
- You can call this method multiple times to add several method names. You can
58
- also use :method: `Symfony\\ Component\\ Validator\\ ValidatorBuilder::addMethodMappings `
57
+ Instead of calling ``addMethodMapping() `` multiple times to add several
58
+ method names, you can also use
59
+ :method: `Symfony\\ Component\\ Validator\\ ValidatorBuilder::addMethodMappings `
59
60
to set an array of supported method names.
60
61
61
- The FileLoaders
62
- ---------------
62
+ The File Loaders
63
+ ----------------
63
64
64
65
The component also provides two file loaders, one to load YAML files and one to
65
66
load XML files. Use
@@ -146,7 +147,7 @@ Caching
146
147
147
148
Using many loaders to load metadata from different places is convenient, but it
148
149
can slow down your application because each file needs to be parsed, validated
149
- and converted to a :class: `Symfony\\ Component\\ Validator\\ Mapping\\ ClassMetadata `
150
+ and converted into a :class: `Symfony\\ Component\\ Validator\\ Mapping\\ ClassMetadata `
150
151
instance. To solve this problem, you can cache the ``ClassMetadata `` information.
151
152
152
153
The Validator component comes with an
0 commit comments