@@ -117,7 +117,7 @@ property name (``first_name`` becomes ``FirstName``) and prefixes it with
117
117
var_dump($accessor->getValue($person, 'first_name')); // 'Wouter'
118
118
119
119
You can override the called getter method using metadata (i.e. annotations or
120
- configuration files). see `Custom method calls and virtual properties in a class `_
120
+ configuration files). See `Custom method calls and virtual properties in a class `_.
121
121
122
122
Using Hassers/Issers
123
123
~~~~~~~~~~~~~~~~~~~~
@@ -310,7 +310,7 @@ see `Enable other Features`_.
310
310
var_dump($person->getWouter()); // array(...)
311
311
312
312
You can override the called setter method using metadata (i.e. annotations or
313
- configuration files). see `Custom method calls and virtual properties in a class `_
313
+ configuration files). See `Custom method calls and virtual properties in a class `_.
314
314
315
315
Checking Property Paths
316
316
-----------------------
@@ -375,7 +375,7 @@ Custom method calls and virtual properties in a class
375
375
-----------------------------------------------------
376
376
377
377
Sometimes you may not want the component to guess which method has to be called
378
- when reading or writing properties. This is specially interesting when property
378
+ when reading or writing properties. This is especially interesting when property
379
379
names are not in English or its singularization is not properly detected.
380
380
381
381
For those cases you can add metadata to the class being accessed so that the
@@ -625,16 +625,14 @@ Or you can pass parameters directly to the constructor (not the recommended way)
625
625
626
626
If you need to enable metadata processing (see
627
627
`Custom method calls and virtual properties in a class `_) you must instantiate
628
- a :class: `Symfony\\ Componente \\ PropertyAcces\\ Mapping\\ Factory\\ MetadataFactoryInterface `
628
+ a :class: `Symfony\\ Component \\ PropertyAcces\\ Mapping\\ Factory\\ MetadataFactoryInterface `
629
629
and use the method `setMetadataFactory ` on the
630
630
:class: `Symfony\\ Component\\ PropertyAccess\\ PropertyAccessorBuilder `. Bundled with
631
631
the component you can find
632
632
a `MetadataFactory ` class that supports different kind of loaders (annotations,
633
- YAML and YML files) called :class: `
634
- Symfony\\ Componente\\ PropertyAcces\\ Mapping\\ Factory\\ LazyLoadingMetadataFactory `.
633
+ YAML and YML files) called :class: `Symfony\\ Component\\ PropertyAcces\\ Mapping\\ Factory\\ LazyLoadingMetadataFactory `.
635
634
636
- Its constructor needs a :class: `
637
- Symfony\\ Component\\ PropertyAccess\\ Mapping\\ Loader\\ LoaderInterface ` which specifies
635
+ Its constructor needs a :class: `Symfony\\ Component\\ PropertyAccess\\ Mapping\\ Loader\\ LoaderInterface ` which specifies
638
636
the source of the metadata information. You can also use a PSR6 compliant cache
639
637
as the second parameter passing a :class: `Psr\\ Cache\\ CacheItemPoolInterface `
640
638
reference.
0 commit comments