Merge branch '2.8' into 3.2

* 2.8:
  Rewriting the service container docs
  Minor reword
  Adding a tip for validation in forms without class
  Added a note about the .htaccess files included by Symfony apps
  Made unmapped field example in forms chapter more descriptive
  [#7507] fix namespace
  Explain better how to enable the ClockMock annotation

Author: weaverryan

components/phpunit_bridge.rst

@@ -215,14 +215,25 @@ The :class:`Symfony\\Bridge\\PhpUnit\\ClockMock` class provided by this bridge
 allows you to mock the PHP's built-in time functions ``time()``,
 ``microtime()``, ``sleep()`` and ``usleep()``.
 
-To use the ``ClockMock`` class in your test, you can:
+To use the ``ClockMock`` class in your test, add the ``@group time-sensitive``
+annotation to its class or methods. This annotation only works when executing
+PHPUnit using the ``vendor/bin/simple-phpunit`` script or when registering the
+following listener in your PHPUnit configuration:
 
-* (**Recommended**) Add the ``@group time-sensitive`` annotation to its class or
-  method;
+.. code-block:: xml
+
+    <!-- phpunit.xml.dist -->
+    <!-- ... -->
+    <listeners>
+        <listener class="\Symfony\Bridge\PhpUnit\SymfonyTestsListener" />
+    </listeners>
+
+.. note::
 
-* Register it manually by calling ``ClockMock::register(__CLASS__)`` and
-  ``ClockMock::withClockMock(true)`` before the test and
-  ``ClockMock::withClockMock(false)`` after the test.
+    If you don't want to use the ``@group time-sensitive`` annotation, you can
+    register the ``ClockMock`` class manually by calling
+    ``ClockMock::register(__CLASS__)`` and ``ClockMock::withClockMock(true)``
+    before the test and ``ClockMock::withClockMock(false)`` after the test.
 
 As a result, the following is guaranteed to work and is no longer a transient
 test::

form/without_class.rst

@@ -106,3 +106,9 @@ but here's a short example:
     .. code-block:: php
 
         new NotBlank(array('groups' => array('create', 'update')));
+
+.. tip::
+
+    If the form is not mapped to an object, every object in your array of
+    submitted data is validated using the ``Symfony\Component\Validator\Constraints\Valid``
+    constraint, unless you :doc:`disable validation </form/disabling_validation>`.

forms.rst

@@ -666,7 +666,8 @@ the choice is ultimately up to you.
         {
             $builder
                 ->add('task')
-                ->add('dueDate', null, array('mapped' => false))
+                ->add('dueDate')
+                ->add('agreeTerms', CheckboxType::class, array('mapped' => false))
                 ->add('save', SubmitType::class)
             ;
         }
@@ -676,11 +677,11 @@ the choice is ultimately up to you.
 
     The field data can be accessed in a controller with::
 
-        $form->get('dueDate')->getData();
+        $form->get('agreeTerms')->getData();
 
     In addition, the data of an unmapped field can also be modified directly::
 
-        $form->get('dueDate')->setData(new \DateTime());
+        $form->get('agreeTerms')->setData(true);
 
 Final Thoughts
 --------------