symfony · fancyweb · Jul 20, 2016 · Jul 20, 2016 · Jul 20, 2016 · Jul 20, 2016
diff --git a/components/property_info.rst b/components/property_info.rst
@@ -5,18 +5,14 @@
 The PropertyInfo Component
 ==========================

-    The PropertyInfo component provides the functionality to get information
-    about class properties using metadata of popular sources.
+    The PropertyInfo component allows you to get information
+    about class properties by using different sources of metadata.

 While the :doc:`PropertyAccess component </components/property_access>`
 allows you to read and write values to/from objects and arrays, the PropertyInfo
-component works solely with class definitions to provide information such
-as data type and visibility about properties within that class.
-
-Similar to PropertyAccess, the PropertyInfo component combines both class
-properties (such as ``$property``) and properties defined via accessor and
-mutator methods such as  ``getProperty()``, ``isProperty()``, ``setProperty()``,
-``addProperty()``, ``removeProperty()``, etc.
+component works solely with class definitions to provide information about the
+data type and visibility - including via getter or setter methods - of the properties
+within that class.

 .. _`components-property-information-installation`:

@@ -39,22 +35,48 @@ Additional dependencies may be required for some of the
 Usage
 -----

-The entry point of this component is a new instance of the
-:class:`Symfony\\Component\\PropertyInfo\\PropertyInfoExtractor`
-class, providing sets of information extractors.
+To use this component, create a new
+:class:`Symfony\\Component\\PropertyInfo\\PropertyInfoExtractor` instance and
+provide it with a set of information extractors.

 .. code-block:: php

    use Symfony\Component\PropertyInfo\PropertyInfoExtractor;
+    use Symfony\Component\PropertyInfo\Extractor\PhpDocExtractor;
+    use Symfony\Component\PropertyInfo\Extractor\ReflectionExtractor;
+    use Example\Namespace\YourAwesomeCoolClass;
+
+    // a full list of extractors is shown further below
+    $phpDocExtractor = new PhpDocExtractor();
+    $reflectionExtractor = new ReflectionExtractor();
+
+    // array of PropertyListExtractorInterface
+    $listExtractors = array($reflectionExtractor);
+
+    // array of PropertyTypeExtractorInterface
+    $typeExtractors = array($phpDocExtractor, $reflectionExtractor);
+
+    // array of PropertyDescriptionExtractorInterface
+    $descriptionExtractors = array($phpDocExtractor);
+
+    // array of PropertyAccessExtractorInterface
+    $accessExtractors = array($reflectionExtractor);

    $propertyInfo = new PropertyInfoExtractor(
-        $arrayOfListExtractors,
-        $arrayOfTypeExtractors,
-        $arrayOfDescriptionExtractors,
-        $arrayOfAccessExtractors
+        $listExtractors,
+        $typeExtractors,
+        $descriptionExtractors,
+        $accessExtractors
    );

-The order of extractor instances within an array matters, as the first non-null
+    // see below for more examples
+    $class = YourAwesomeCoolClass::class;
+    $properties = $propertyInfo->getProperties($class);
+
+Extractor Ordering
+~~~~~~~~~~~~~~~~~~
+
+The order of extractor instances within an array matters: the first non-null
 result will be returned. That is why you must provide each category of extractors
 as a separate array, even if an extractor provides information for more than
 one category.
@@ -98,21 +120,26 @@ Extractable Information
 -----------------------

 The :class:`Symfony\\Component\\PropertyInfo\\PropertyInfoExtractor`
-class exposes public methods to extract four types of information: list,
-type, description and access information. The first type of information is
-about the class, while the remaining three are about the individual properties.
+class exposes public methods to extract four types of information:
+
+* :ref:`*List* of properties <property-info-list>`: `getProperties()`
+* :ref:`Property *type* <property-info-type>`: `getTypes()`
+* :ref:`Property *description* <property-info-description>`: `getShortDescription()` and `getLongDescription()`
+* :ref:`Property *access* details <property-info-access>`: `isReadable()` and `isWritable()`

 .. note::

-    When specifiying a class that the PropertyInfo component should work
-    with, use the fully-qualified class name. Do not directly pass an object
-    as some extractors (the
-    :class:`Symfony\\Component\\PropertyInfo\\Extractor\\SerializerExtractor`
-    is an example) may not automatically resolve objects to their class
-    names - use the ``get_class()`` function.
+    Be sure to pass a *class* name, not an object to the extractor methods::
+
+        // bad! It may work, but not with all extractors
+        $propertyInfo->getProperties($awesomeObject);

-    Since the PropertyInfo component requires PHP 5.5 or greater, you can
-    also make use of the `class constant`_.
+        // Good!
+        $propertyInfo->getProperties(get_class($awesomeObject));
+        $propertyInfo->getProperties('Example\Namespace\YourAwesomeClass');
+        $propertyInfo->getProperties(YourAwesomeClass::class);
+
+.. _property-info-list:

 List Information
 ~~~~~~~~~~~~~~~~
@@ -134,6 +161,8 @@ containing each property name as a string.
      }
    */

+.. _property-info-type:
+
 Type Information
 ~~~~~~~~~~~~~~~~

@@ -161,6 +190,10 @@ for a property.
      }
    */

+See :ref:`components-property-info-type` for info about the ``Type`` class.
+
+.. _property-info-description:
+
 Description Information
 ~~~~~~~~~~~~~~~~~~~~~~~

@@ -186,6 +219,8 @@ strings.
        It can span multiple lines.
    */

+.. _property-info-access:
+
 Access Information
 ~~~~~~~~~~~~~~~~~~

@@ -200,6 +235,11 @@ provide whether properties are readable or writable as booleans.
    $propertyInfo->isWritable($class, $property);
    // Example Result: bool(false)

+The :class:`Symfony\\Component\\PropertyInfo\\Extractor\\ReflectionExtractor` looks
+for getter/isser/setter method in addition to whether or not a property is public
+to determine if it's accessible. This based on how the :doc:`PropertyAccess </components/property_access>`
+works.
+
 .. tip::

    The main :class:`Symfony\\Component\\PropertyInfo\\PropertyInfoExtractor`
@@ -216,10 +256,9 @@ Type Objects
 ------------

 Compared to the other extractors, type information extractors provide much
-more information than can be represented as simple scalar values - because
-of this, type extractors return an array of objects. The array will contain
-an instance of the :class:`Symfony\\Component\\PropertyInfo\\Type`
-class for each type that the property supports.
+more information than can be represented as simple scalar values. Because
+of this, type extractors return an array of :class:`Symfony\\Component\\PropertyInfo\\Type`
+objects for each type that the property supports.

 For example, if a property supports both ``integer`` and ``string`` (via
 the ``@return int|string`` annotation),
@@ -233,15 +272,12 @@ class.
    instance. The :class:`Symfony\\Component\\PropertyInfo\\Extractor\\PhpDocExtractor`
    is currently the only extractor that returns multiple instances in the array.

-Each object will provide 6 attributes; the first four (built-in type, nullable,
-class and collection) are scalar values and the last two (collection key
-type and collection value type) are more instances of the :class:`Symfony\\Component\\PropertyInfo\\Type`
-class again if collection is ``true``.
+Each object will provide 6 attributes, available in the 6 methods:

 .. _`components-property-info-type-builtin`:

-Built-in Type
-~~~~~~~~~~~~~
+Type::getBuiltInType()
+~~~~~~~~~~~~~~~~~~~~~~

 The :method:`Type::getBuiltinType() <Symfony\\Component\\PropertyInfo\\Type::getBuiltinType>`
 method will return the built-in PHP data type, which can be one of 9 possible
@@ -251,22 +287,22 @@ string values: ``array``, ``bool``, ``callable``, ``float``, ``int``, ``null``,
 Constants inside the :class:`Symfony\\Component\\PropertyInfo\\Type`
 class, in the form ``Type::BUILTIN_TYPE_*``, are provided for convenience.

-Nullable
-~~~~~~~~
+Type::isNullable()
+~~~~~~~~~~~~~~~~~~

 The :method:`Type::isNullable() <Symfony\\Component\\PropertyInfo\\Type::isNullable>`
 method will return a boolean value indicating whether the property parameter
 can be set to ``null``.

-Class
-~~~~~
+Type::getClassName()
+~~~~~~~~~~~~~~~~~~~~

 If the :ref:`built-in PHP data type <components-property-info-type-builtin>`
 is ``object``, the :method:`Type::getClassName() <Symfony\\Component\\PropertyInfo\\Type::getClassName>`
 method will return the fully-qualified class or interface name accepted.

-Collection
-~~~~~~~~~~
+Type::isCollection()
+~~~~~~~~~~~~~~~~~~~~

 The :method:`Type::isCollection() <Symfony\\Component\\PropertyInfo\\Type::isCollection>`
 method will return a boolean value indicating if the property parameter is
@@ -278,8 +314,8 @@ this returns ``true`` if:
 * The mutator method the property is derived from has a prefix of ``add``
  or ``remove`` (which are defined as the list of array mutator prefixes).

-Collection Key & Value Types
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Type::getCollectionKeyType() & Type::getCollectionValueType()
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 If the property is a collection, additional type objects may be returned
 for both the key and value types of the collection (if the information is
@@ -312,13 +348,14 @@ Using PHP reflection, the :class:`Symfony\\Component\\PropertyInfo\\Extractor\\R
 provides list, type and access information from setter and accessor methods.
 It can also provide return and scalar types for PHP 7+.

-This service is automatically registered with the ``property_info`` service.
+This service is automatically registered with the ``property_info`` service in
+the Symfony Framework.

 .. code-block:: php

    use Symfony\Component\PropertyInfo\Extractor\ReflectionExtractor;

-    $reflectionExtractor = new ReflectionExtractor;
+    $reflectionExtractor = new ReflectionExtractor();

    // List information.
    $reflectionExtractor->getProperties($class);
@@ -338,13 +375,14 @@ PhpDocExtractor
 Using `phpDocumentor Reflection`_ to parse property and method annotations,
 the :class:`Symfony\\Component\\PropertyInfo\\Extractor\\PhpDocExtractor`
 provides type and description information. This extractor is automatically
-registered with the ``property_info`` providing its dependencies are detected.
+registered with the ``property_info`` in the Symfony Framework *if* the dependent
+library is present.

 .. code-block:: php

    use Symfony\Component\PropertyInfo\Extractor\PhpDocExtractor;

-    $phpDocExtractor = new PhpDocExtractor;
+    $phpDocExtractor = new PhpDocExtractor();

    // Type information.
    $phpDocExtractor->getTypes($class, $property);
@@ -359,10 +397,11 @@ SerializerExtractor

    This extractor depends on the `symfony/serializer`_ library.

-Using groups metadata from the :doc:`Serializer component </components/serializer>`,
+Using :ref:`groups metadata <serializer-using-serialization-groups-annotations>`
+from the :doc:`Serializer component </components/serializer>`,
 the :class:`Symfony\\Component\\PropertyInfo\\Extractor\\SerializerExtractor`
-provides list information. This extractor is not registered automatically
-with the ``property_info`` service.
+provides list information. This extractor is *not* registered automatically
+with the ``property_info`` service in the Symfony Framework.

 .. code-block:: php

@@ -389,9 +428,8 @@ DoctrineExtractor

 Using entity mapping data from `Doctrine ORM`_, the
 :class:`Symfony\\Bridge\\Doctrine\\PropertyInfo\\DoctrineExtractor`
- located in the Doctrine bridge - provides list and type information.
-This extractor is not registered automatically with the ``property_info``
-service.
+provides list and type information. This extractor is not registered automatically
+with the ``property_info`` service in the Symfony Framework.

 .. code-block:: php

@@ -440,4 +478,3 @@ service by defining it as a service with one or more of the following
 .. _`symfony/serializer`: https://packagist.org/packages/symfony/serializer
 .. _`symfony/doctrine-bridge`: https://packagist.org/packages/symfony/doctrine-bridge
 .. _`doctrine/orm`: https://packagist.org/packages/doctrine/orm
-.. _`class constant`: http://php.net/manual/en/language.oop5.basic.php#language.oop5.basic.class.class
diff --git a/form/unit_testing.rst b/form/unit_testing.rst
@@ -127,7 +127,7 @@ make sure the ``FormRegistry`` uses the created instance::
        protected function setUp()
        {
            // mock any dependencies
-            $this->entityManager = $this->getMock('Doctrine\Common\Persistence\ObjectManager');
+            $this->entityManager = $this->getMockBuilder('Doctrine\Common\Persistence\ObjectManager')->getMock();

            parent::setUp();
        }
@@ -178,7 +178,7 @@ allows you to return a list of extensions to register::

        protected function getExtensions()
        {
-            $this->validator = $this->getMock(
+            $this->validator = $this->createMock(
                'Symfony\Component\Validator\Validator\ValidatorInterface'
            );
            $this->validator

diff --git a/reference/configuration/framework.rst b/reference/configuration/framework.rst
@@ -42,9 +42,9 @@ Configuration
    * `only_exceptions`_
    * `only_master_requests`_
    * `dsn`_
-    * `username`_
-    * `password`_
-    * `lifetime`_
+    * `username`_ (deprecated since 2.8)
+    * `password`_ (deprecated since 2.8)
+    * `lifetime`_ (deprecated since 2.8)
    * `matcher`_
        * `ip`_
        * :ref:`path <reference-profiler-matcher-path>`
@@ -559,20 +559,33 @@ The DSN where to store the profiling information.
 username
 ........

-**type**: ``string`` **default**: ``''``
+.. caution::

-When needed, the username for the profiling storage.
+    The ``framework.profiler.username`` setting is deprecated since Symfony 2.8
+    and will be removed in Symfony 3.0.
+
+**type**: ``string`` **default**: ``''``

 password
 ........

+.. caution::
+
+    The ``framework.profiler.password`` setting is deprecated since Symfony 2.8
+    and will be removed in Symfony 3.0.
+
 **type**: ``string`` **default**: ``''``

 When needed, the password for the profiling storage.

 lifetime
 ........

+.. caution::
+
+    The ``framework.profiler.lifetime`` setting is deprecated since Symfony 2.8
+    and will be removed in Symfony 3.0.
+
 **type**: ``integer`` **default**: ``86400``

 The lifetime of the profiling storage in seconds. The data will be deleted
@@ -1474,9 +1487,9 @@ Full Default Configuration
                only_exceptions:      false
                only_master_requests: false
                dsn:                  file:%kernel.cache_dir%/profiler
-                username:
-                password:
-                lifetime:             86400
+                username:             ~     # deprecated since 2.8, to be removed in 3.0.
+                password:             ~     # deprecated since 2.8, to be removed in 3.0.
+                lifetime:             86400 # deprecated since 2.8, to be removed in 3.0.
                matcher:
                    ip:                   ~


diff --git a/service_container/tags.rst b/service_container/tags.rst
@@ -195,7 +195,7 @@ Create a Compiler Pass
 ~~~~~~~~~~~~~~~~~~~~~~

 You can now use a :ref:`compiler pass <components-di-separate-compiler-passes>` to ask the
-container for any services with the ``acme_mailer.transport`` tag::
+container for any services with the ``app.mail_transport`` tag::

    // src/AppBundle/DependencyInjection/Compiler/MailTransportPass.php
    namespace AppBundle\DependencyInjection\Compiler;

diff --git a/testing/database.rst b/testing/database.rst
@@ -73,7 +73,7 @@ it's easy to pass a mock object within a test::
        public function testCalculateTotalSalary()
        {
            // First, mock the object to be used in the test
-            $employee = $this->getMock(Employee::class);
+            $employee = $this->createMock(Employee::class);
            $employee->expects($this->once())
                ->method('getSalary')
                ->will($this->returnValue(1000));