Merge branch '2.7' into 2.8

* 2.7:
  use namespaced PHPUnit classes
  Update event_dispatcher.rst for consistency
  Made 'create-user' command consistent.
  Update without_class.rst
  Fix typo
  Fixed the way flash messages are retrieved in the template
  Minor improvement for the default console command article

Author: xabbuh

components/console/changing_default_command.rst

@@ -28,7 +28,7 @@ name to the ``setDefaultCommand()`` method::
         }
     }
 
-Executing the application and changing the default Command::
+Executing the application and changing the default command::
 
     // application.php
 
@@ -53,9 +53,10 @@ This will print the following to the command line:
 
     Hello World
 
-.. tip::
+.. caution::
 
-    This feature has a limitation: you cannot use it with any Command arguments.
+    This feature has a limitation: you cannot pass any argument or option to
+    the default command because they are ignored.
 
 Learn More!
 -----------

components/event_dispatcher.rst

@@ -135,7 +135,7 @@ A call to the dispatcher's ``addListener()`` method associates any valid
 PHP callable to an event::
 
     $listener = new AcmeListener();
-    $dispatcher->addListener('acme.action', array($listener, 'onFooAction'));
+    $dispatcher->addListener('acme.foo.action', array($listener, 'onFooAction'));
 
 The ``addListener()`` method takes up to three arguments:
 
@@ -161,12 +161,12 @@ The ``addListener()`` method takes up to three arguments:
 
         use Symfony\Component\EventDispatcher\Event;
 
-        $dispatcher->addListener('foo.action', function (Event $event) {
-            // will be executed when the foo.action event is dispatched
+        $dispatcher->addListener('acme.foo.action', function (Event $event) {
+            // will be executed when the acme.foo.action event is dispatched
         });
 
 Once a listener is registered with the dispatcher, it waits until the event
-is notified. In the above example, when the ``foo.action`` event is dispatched,
+is notified. In the above example, when the ``acme.foo.action`` event is dispatched,
 the dispatcher calls the ``AcmeListener::onFooAction()`` method and passes
 the ``Event`` object as the single argument::
 
@@ -216,7 +216,7 @@ determine which instance is passed.
         // register your event listener service
         $listener = new Definition(\AcmeListener::class);
         $listener->addTag('kernel.event_listener', array(
-            'event' => 'foo.action',
+            'event' => 'acme.foo.action',
             'method' => 'onFooAction',
         ));
         $containerBuilder->setDefinition('listener_service_id', $listener);

components/var_dumper.rst

@@ -128,7 +128,9 @@ This will provide you with two new assertions:
 
 Example::
 
-    class ExampleTest extends \PHPUnit_Framework_TestCase
+    use PHPUnit\Framework\TestCase;
+
+    class ExampleTest extends TestCase
     {
         use \Symfony\Component\VarDumper\Test\VarDumperTestTrait;
 

console.rst

@@ -50,14 +50,14 @@ method. Then you can optionally define a help message and the
     {
         $this
             // the name of the command (the part after "app/console")
-            ->setName('app:create-users')
+            ->setName('app:create-user')
 
             // the short description shown while running "php app/console list"
-            ->setDescription('Creates new users.')
+            ->setDescription('Creates a new user.')
 
             // the full command description shown when running the command with
             // the "--help" option
-            ->setHelp('This command allows you to create users...')
+            ->setHelp('This command allows you to create a user...')
         ;
     }
 
@@ -68,7 +68,7 @@ After configuring the command, you can execute it in the terminal:
 
 .. code-block:: terminal
 
-    $ php app/console app:create-users
+    $ php app/console app:create-user
 
 As you might expect, this command will do nothing as you didn't write any logic
 yet. Add your own logic inside the ``execute()`` method, which has access to the
@@ -258,7 +258,7 @@ console::
 
     When using the Console component in a standalone project, use
     :class:`Symfony\\Component\\Console\\Application <Symfony\\Component\\Console\\Application>`
-    and extend the normal ``\PHPUnit_Framework_TestCase``.
+    and extend the normal ``\PHPUnit\Framework\TestCase``.
 
 To be able to use the fully set up service container for your console tests
 you can extend your test from

controller.rst

@@ -424,19 +424,19 @@ read any flash messages from the session:
         {# app/Resources/views/base.html.twig #}
 
         {# you can read and display just one flash message type... #}
-        {% for flash_message in app.session.flash('notice') %}
+        {% for flash_message in app.session.flashBag.get('notice') %}
             <div class="flash-notice">
                 {{ flash_message }}
             </div>
         {% endfor %}
 
         {# ...or you can read and display every flash message available #}
-        {% for type, flash_messages in app.session.flashes %}
+        {% for type, flash_messages in app.session.flashBag.all %}
             {% for flash_message in flash_messages %}
                 <div class="flash-{{ type }}">
                     {{ flash_message }}
                 </div>
-            {% endif %}
+            {% endfor %}
         {% endfor %}
 
     .. code-block:: html+php

create_framework/http_foundation.rst

@@ -58,7 +58,9 @@ snippet of PHP code is not natural and feels ugly. Here is a tentative PHPUnit
 unit test for the above code::
 
     // framework/test.php
-    class IndexTest extends \PHPUnit_Framework_TestCase
+    use PHPUnit\Framework\TestCase;
+
+    class IndexTest extends TestCase
     {
         public function testHello()
         {

create_framework/unit_testing.rst

@@ -72,13 +72,14 @@ We are now ready to write our first test::
     // example.com/tests/Simplex/Tests/FrameworkTest.php
     namespace Simplex\Tests;
 
+    use PHPUnit\Framework\TestCase;
     use Simplex\Framework;
     use Symfony\Component\HttpFoundation\Request;
     use Symfony\Component\HttpKernel\Controller\ControllerResolverInterface;
     use Symfony\Component\Routing;
     use Symfony\Component\Routing\Exception\ResourceNotFoundException;
 
-    class FrameworkTest extends \PHPUnit_Framework_TestCase
+    class FrameworkTest extends TestCase
     {
         public function testNotFoundHandling()
         {

form/without_class.rst

@@ -102,7 +102,7 @@ but here's a short example:
     If you are using validation groups, you need to either reference the
     ``Default`` group when creating the form, or set the correct group on
     the constraint you are adding.
+    
+    .. code-block:: php
 
-.. code-block:: php
-
-    new NotBlank(array('groups' => array('create', 'update'))
+        new NotBlank(array('groups' => array('create', 'update')))

testing.rst

@@ -71,8 +71,9 @@ of your bundle::
     namespace AppBundle\Tests\Util;
 
     use AppBundle\Util\Calculator;
+    use PHPUnit\Framework\TestCase;
 
-    class CalculatorTest extends \PHPUnit_Framework_TestCase
+    class CalculatorTest extends TestCase
     {
         public function testAdd()
         {

testing/database.rst

@@ -63,8 +63,9 @@ it's easy to pass a mock object within a test::
     use AppBundle\Salary\SalaryCalculator;
     use Doctrine\ORM\EntityRepository;
     use Doctrine\Common\Persistence\ObjectManager;
+    use PHPUnit\Framework\TestCase;
 
-    class SalaryCalculatorTest extends \PHPUnit_Framework_TestCase
+    class SalaryCalculatorTest extends TestCase
     {
         public function testCalculateTotalSalary()
         {