2121-----
2222
2323The entry point of this component is the
24- :method: `PropertyAccess::createPropertyAccessor< Symfony\\ Component\\ PropertyAccess\\ PropertyAccess::createPropertyAccessor> `
24+ :method: `Symfony\\ Component\\ PropertyAccess\\ PropertyAccess::createPropertyAccessor `
2525factory. This factory will create a new instance of the
2626:class: `Symfony\\ Component\\ PropertyAccess\\ PropertyAccessor ` class with the
2727default configuration::
@@ -34,8 +34,8 @@ Reading from Arrays
3434-------------------
3535
3636You can read an array with the
37- :method: `PropertyAccessor::getValue< Symfony\\ Component\\ PropertyAccess\\ PropertyAccessor::getValue> `
38- method. This is done using the index notation that is used in PHP::
37+ :method: `Symfony\\ Component\\ PropertyAccess\\ PropertyAccessor::getValue ` method.
38+ This is done using the index notation that is used in PHP::
3939
4040 // ...
4141 $person = [
@@ -175,7 +175,7 @@ Accessing a non Existing Property Path
175175 Symfony 4.3.
176176
177177By default a :class: `Symfony\\ Component\\ PropertyAccess\\ Exception\\ NoSuchPropertyException `
178- is thrown if the property path passed to :method: `PropertyAccessor::getValue< Symfony\\ Component\\ PropertyAccess\\ PropertyAccessor::getValue> `
178+ is thrown if the property path passed to :method: `Symfony\\ Component\\ PropertyAccess\\ PropertyAccessor::getValue `
179179does not exist. You can change this behavior using the
180180:method: `Symfony\\ Component\\ PropertyAccess\\ PropertyAccessorBuilder::disableExceptionOnInvalidPropertyPath `
181181method::
@@ -259,16 +259,15 @@ enable this feature by using :class:`Symfony\\Component\\PropertyAccess\\Propert
259259.. caution ::
260260
261261 The ``__call() `` feature is disabled by default, you can enable it by calling
262- :method: `PropertyAccessorBuilder::enableMagicCall< Symfony\\ Component\\ PropertyAccess\\ PropertyAccessorBuilder::enableMagicCall> `
262+ :method: `Symfony\\ Component\\ PropertyAccess\\ PropertyAccessorBuilder::enableMagicCall `
263263 see `Enable other Features `_.
264264
265265Writing to Arrays
266266-----------------
267267
268268The ``PropertyAccessor `` class can do more than just read an array, it can
269269also write to an array. This can be achieved using the
270- :method: `PropertyAccessor::setValue<Symfony\\ Component\\ PropertyAccess\\ PropertyAccessor::setValue> `
271- method::
270+ :method: `Symfony\\ Component\\ PropertyAccess\\ PropertyAccessor::setValue ` method::
272271
273272 // ...
274273 $person = [];
@@ -404,20 +403,18 @@ Checking Property Paths
404403-----------------------
405404
406405When you want to check whether
407- :method: `PropertyAccessor::getValue<Symfony\\ Component\\ PropertyAccess\\ PropertyAccessor::getValue> `
408- can safely be called without actually calling that method, you can use
409- :method: `PropertyAccessor::isReadable<Symfony\\ Component\\ PropertyAccess\\ PropertyAccessor::isReadable> `
410- instead::
406+ :method: `Symfony\\ Component\\ PropertyAccess\\ PropertyAccessor::getValue ` can
407+ safely be called without actually calling that method, you can use
408+ :method: `Symfony\\ Component\\ PropertyAccess\\ PropertyAccessor::isReadable ` instead::
411409
412410 $person = new Person();
413411
414412 if ($propertyAccessor->isReadable($person, 'firstName')) {
415413 // ...
416414 }
417415
418- The same is possible for :method: `PropertyAccessor::setValue<Symfony\\ Component\\ PropertyAccess\\ PropertyAccessor::setValue> `:
419- Call the
420- :method: `PropertyAccessor::isWritable<Symfony\\ Component\\ PropertyAccess\\ PropertyAccessor::isWritable> `
416+ The same is possible for :method: `Symfony\\ Component\\ PropertyAccess\\ PropertyAccessor::setValue `:
417+ Call the :method: `Symfony\\ Component\\ PropertyAccess\\ PropertyAccessor::isWritable `
421418method to find out whether a property path can be updated::
422419
423420 $person = new Person();
0 commit comments