Merge branch '2.7' into 2.8

* 2.7:
  [#8282] fix regex delimiters
  Add missing comment
  validateValue() is deprecated in 3.0
  prefer getObject as getEntity is deprecated
  Update serializer.rst
  [#8308] fix commands order
  Update NotIdenticalTo.rst
  Correct psr/log package name
  Update debugging.rst
  Update group_service_resolver.rst
  Update remember_me.rst
  Update expression_language.rst
  [VarDumper] s/dump.dump_destination/debug.dump_destination/
  fix schema_filter example
  fix form collection label not correct

Author: xabbuh

components/console/logger.rst

@@ -9,7 +9,7 @@ The Console component comes with a standalone logger complying with the
 be sent to the :class:`Symfony\\Component\\Console\\Output\\OutputInterface`
 instance passed as a parameter to the constructor.
 
-The logger does not have any external dependency except ``php-fig/log``.
+The logger does not have any external dependency except ``psr/log``.
 This is useful for console applications and commands needing a lightweight
 PSR-3 compliant logger::
 

components/serializer.rst

@@ -397,7 +397,7 @@ class extending :class:`Symfony\\Component\\Serializer\\Normalizer\\AbstractNorm
 including :class:`Symfony\\Component\\Serializer\\Normalizer\\GetSetMethodNormalizer`
 and :class:`Symfony\\Component\\Serializer\\Normalizer\\PropertyNormalizer`::
 
-    use Symfony\Component\Serializer\Encoder\JsonEncoder
+    use Symfony\Component\Serializer\Encoder\JsonEncoder;
     use Symfony\Component\Serializer\Normalizer\ObjectNormalizer;
     use Symfony\Component\Serializer\Serializer;
 

components/var_dumper.rst

@@ -101,7 +101,7 @@ Choosing between both is mostly a matter of personal taste, still:
   be suited to your use case (e.g. you shouldn't use it in an HTML
   attribute or a ``<script>`` tag).
 
-This behavior can be changed by configuring the ``dump.dump_destination``
+This behavior can be changed by configuring the ``debug.dump_destination``
 option. Read more about this and other options in
 :doc:`the DebugBundle configuration reference </reference/configuration/debug>`.
 

debug/debugging.rst

@@ -76,6 +76,9 @@ that can help you visualize and find the information.
 ``debug:config``
     Shows all configured bundles, their class and their alias.
 
+``debug:event-dispatcher``
+    Displays information about all the registered listeners in the event dispatcher.
+
 ``debug:router``
     Displays information about all configured routes in the application as a
     table with the name, method, scheme, host and path for each route.

doctrine/event_listeners_subscribers.rst

@@ -194,7 +194,7 @@ interface and have an event method for each event it subscribes to::
 
         public function index(LifecycleEventArgs $args)
         {
-            $entity = $args->getEntity();
+            $entity = $args->getObject();
 
             // perhaps you only want to act on some "Product" entity
             if ($entity instanceof Product) {

form/form_collections.rst

@@ -130,7 +130,8 @@ Notice that you embed a collection of ``TagType`` forms using the
             $builder->add('description');
 
             $builder->add('tags', CollectionType::class, array(
-                'entry_type' => TagType::class
+                'entry_type' => TagType::class,
+                'entry_options' => array('label' => false),
             ));
         }
 
@@ -285,8 +286,9 @@ add the ``allow_add`` option to your collection field::
         $builder->add('description');
 
         $builder->add('tags', CollectionType::class, array(
-            'entry_type'   => TagType::class,
-            'allow_add'    => true,
+            'entry_type' => TagType::class,
+            'entry_options' => array('label' => false),
+            'allow_add' => true,
         ));
     }
 
@@ -392,9 +394,15 @@ one example:
         // get the new index
         var index = $collectionHolder.data('index');
 
+        var newForm = prototype;
+        // You need this only if you didn't set 'label' => false in your tags field in TaskType
+        // Replace '__name__label__' in the prototype's HTML to
+        // instead be a number based on how many items we have
+        // newForm = newForm.replace(/__name__label__/g, index);
+        
         // Replace '__name__' in the prototype's HTML to
         // instead be a number based on how many items we have
-        var newForm = prototype.replace(/__name__/g, index);
+        newForm = newForm.replace(/__name__/g, index);
 
         // increase the index with one for the next item
         $collectionHolder.data('index', index + 1);

forms.rst

@@ -658,6 +658,7 @@ the choice is ultimately up to you.
     good idea to explicitly specify the ``data_class`` option by adding the
     following to your form type class::
 
+        // src/AppBundle/Form/TaskType.php
         use AppBundle\Entity\Task;
         use Symfony\Component\OptionsResolver\OptionsResolver;
 

reference/configuration/doctrine.rst

@@ -24,7 +24,7 @@ Full Default Configuration
                         commented:            true
                 # If defined, all the tables whose names match this regular expression are ignored
                 # by the schema tool (in this example, any table name starting with `wp_`)
-                #schema_filter:               "/^wp_/"
+                #schema_filter:               '/^(?!wp_)/'
 
                 connections:
                     # A collection of different named connections (e.g. default, conn2, etc)

reference/constraints/NotIdenticalTo.rst

@@ -121,6 +121,6 @@ message
 
 **type**: ``string`` **default**: ``This value should not be identical to {{ compared_value_type }} {{ compared_value }}.``
 
-This is the message that will be shown if the value is not equal.
+This is the message that will be shown if the value is identical.
 
 .. include:: /reference/constraints/_payload-option.rst.inc

security/remember_me.rst

@@ -247,7 +247,7 @@ In the following example, the action is only allowed if the user has the
 .. code-block:: php
 
     // ...
-    use Symfony\Component\Security\Core\Exception\AccessDeniedException
+    use Symfony\Component\Security\Core\Exception\AccessDeniedException;
 
     // ...
     public function editAction()

service_container/expression_language.rst

@@ -24,15 +24,15 @@ of the new ``mailer_configuration`` service? One way is to use an expression:
 
     .. code-block:: yaml
 
-        # app/config/config.yml
+        # app/config/services.yml
         services:
             my_mailer:
                 class:     AppBundle\Mailer
                 arguments: ["@=service('mailer_configuration').getMailerMethod()"]
 
     .. code-block:: xml
 
-        <!-- app/config/config.xml -->
+        <!-- app/config/services.xml -->
         <?xml version="1.0" encoding="UTF-8" ?>
         <container xmlns="http://symfony.com/schema/dic/services"
             xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -48,7 +48,7 @@ of the new ``mailer_configuration`` service? One way is to use an expression:
 
     .. code-block:: php
 
-        // app/config/config.php
+        // app/config/services.php
         use AppBundle\Mailer;
         use Symfony\Component\ExpressionLanguage\Expression;
 

validation/group_service_resolver.rst

@@ -47,7 +47,7 @@ Then in your form, inject the resolver and set it as the ``validation_groups``.
     namespace AppBundle\Form;
 
     use AppBundle\Validator\ValidationGroupResolver;
-    use Symfony\Component\Form\AbstractType
+    use Symfony\Component\Form\AbstractType;
     use Symfony\Component\OptionsResolver\OptionsResolver;
 
     class MyClassType extends AbstractType

validation/raw_values.rst

@@ -72,7 +72,7 @@ Validation of arrays is possible using the ``Collection`` constraint::
         'password' => new Assert\Length(array('min' => 60)),
     ));
 
-    $violations = $validator->validateValue($input, $constraint);
+    $violations = $validator->validate($input, $constraint);
 
 The ``validate()`` method returns a :class:`Symfony\\Component\\Validator\\ConstraintViolationList`
 object, which acts just like an array of errors. Each error in the collection