Merge branch '4.0'

* 4.0:
  Update collection.rst
  Mention that PSR-1 doesn't recommend CamelCase or anything else
  Fixed the XML and PHP config instead of the YAML config
  Use controller method injection instead of the constructor
  Add missing references
  Updated documentation to reflect best practice of using Dependency Injection over Container. Includes changes from PR symfony#8985
  Removed "Accessing the Container Directly"
  minor symfony#8091 Update js-datepicker usage for new jQuery UI (AdrianBorodziuk, javiereguiluz)
  minor symfony#8983 cross-reference console command testing from testing guide (dbu)
  Fix YAML config bug
  Removed invalid examples
  commands are automatically registered in symfony full stack
  update forms.rst

Author: javiereguiluz

best_practices/security.rst

@@ -238,12 +238,20 @@ more advanced use-case, you can always do the same security check in PHP:
         // equivalent code without using the "denyAccessUnlessGranted()" shortcut:
         //
         // use Symfony\Component\Security\Core\Exception\AccessDeniedException;
+        // use Symfony\Component\Security\Core\Authorization\AuthorizationCheckerInterface
+        //
+        // ...
+        //
+        // public function __construct(AuthorizationCheckerInterface $authorizationChecker) {
+        //      $this->authorizationChecker = $authorizationChecker;
+        // }
+        //
         // ...
         //
-        // if (!$this->get('security.authorization_checker')->isGranted('edit', $post)) {
+        // if (!$this->authorizationChecker->isGranted('edit', $post)) {
         //    throw $this->createAccessDeniedException();
         // }
-
+        //
         // ...
     }
 
@@ -357,14 +365,22 @@ via the even easier shortcut in a controller:
 
         $this->denyAccessUnlessGranted('edit', $post);
 
-        // or without the shortcut:
-        //
         // use Symfony\Component\Security\Core\Exception\AccessDeniedException;
+        // use Symfony\Component\Security\Core\Authorization\AuthorizationCheckerInterface
+        //
         // ...
         //
-        // if (!$this->get('security.authorization_checker')->isGranted('edit', $post)) {
+        // public function __construct(AuthorizationCheckerInterface $authorizationChecker) {
+        //      $this->authorizationChecker = $authorizationChecker;
+        // }
+        //
+        // ...
+        //
+        // if (!$this->authorizationChecker->isGranted('edit', $post)) {
         //    throw $this->createAccessDeniedException();
         // }
+        //
+        // ...
     }
 
 Learn More

components/serializer.rst

@@ -459,8 +459,9 @@ CamelCase to snake_case
 ~~~~~~~~~~~~~~~~~~~~~~~
 
 In many formats, it's common to use underscores to separate words (also known
-as snake_case). However, PSR-1 specifies that the preferred style for PHP
-properties and methods is CamelCase.
+as snake_case). However, in Symfony applications is common to use CamelCase to
+name properties (even though the `PSR-1 standard`_ doesn't recommend any
+specific case for property names).
 
 Symfony provides a built-in name converter designed to transform between
 snake_case and CamelCased styles during serialization and deserialization
@@ -994,6 +995,7 @@ Learn more
     A popular alternative to the Symfony Serializer Component is the third-party
     library, `JMS serializer`_ (released under the Apache license, so incompatible with GPLv2 projects).
 
+.. _`PSR-1 standard`: http://www.php-fig.org/psr/psr-1/
 .. _`JMS serializer`: https://github.com/schmittjoh/serializer
 .. _Packagist: https://packagist.org/packages/symfony/serializer
 .. _RFC3339: https://tools.ietf.org/html/rfc3339#section-5.8

console.rst

@@ -299,7 +299,6 @@ you can extend your test from
             $kernel->boot();
 
             $application = new Application($kernel);
-            $application->add(new CreateUserCommand());
 
             $command = $application->find('app:create-user');
             $commandTester = new CommandTester($command);

controller.rst

@@ -290,33 +290,6 @@ in your controllers.
 
 For more information about services, see the :doc:`/service_container` article.
 
-.. _controller-access-services-directly:
-
-Accessing the Container Directly
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-If you extend the base ``Controller`` class, you can access :ref:`public services <container-public>`
-via the :method:`Symfony\\Bundle\\FrameworkBundle\\Controller\\Controller::get`
-method. Here are several common services you might need::
-
-    $templating = $this->get('templating');
-
-    $router = $this->get('router');
-
-    $mailer = $this->get('mailer');
-
-    // you can also fetch parameters
-    $someParameter = $this->getParameter('some_parameter');
-
-If you receive an error like:
-
-.. code-block:: text
-
-    You have requested a non-existent service "my_service_id"
-
-Check to make sure the service exists (use :ref:`debug:container <container-debug-container>`)
-and that it's :ref:`public <container-public>`.
-
 .. index::
    single: Controller; Managing errors
    single: Controller; 404 pages

doctrine/multiple_entity_managers.rst

@@ -231,11 +231,14 @@ the default entity manager (i.e. ``default``) is returned::
 
     // ...
 
+    use Doctrine\ORM\EntityManagerInterface;
+
     class UserController extends Controller
     {
-        public function indexAction()
+        public function indexAction(EntityManagerInterface $em)
         {
-            // All 3 return the "default" entity manager
+            // These methods also return the default entity manager, but it's preferred
+            // to get it by inyecting EntityManagerInterface in the action method
             $em = $this->getDoctrine()->getManager();
             $em = $this->getDoctrine()->getManager('default');
             $em = $this->get('doctrine.orm.default_entity_manager');

event_dispatcher.rst

@@ -91,9 +91,7 @@ using a special "tag":
                 http://symfony.com/schema/dic/services/services-1.0.xsd">
 
             <services>
-                <service id="app.exception_listener"
-                    class="App\EventListener\ExceptionListener">
-
+                <service id="AppBundle\EventListener\ExceptionListener">
                     <tag name="kernel.event_listener" event="kernel.exception" />
                 </service>
             </services>
@@ -105,7 +103,7 @@ using a special "tag":
         use App\EventListener\ExceptionListener;
 
         $container
-            ->register('app.exception_listener', ExceptionListener::class)
+            ->autowire(ExceptionListener::class)
             ->addTag('kernel.event_listener', array('event' => 'kernel.exception'))
         ;
 

forms.rst

@@ -317,6 +317,12 @@ valid, but whether or not the ``$task`` object is valid after the form has
 applied the submitted data to it. Calling ``$form->isValid()`` is a shortcut
 that asks the ``$task`` object whether or not it has valid data.
 
+Before using validation, add support for it in your application:
+
+.. code-block:: terminal
+
+    $ composer require validator
+
 Validation is done by adding a set of rules (called constraints) to a class. To
 see this in action, add validation constraints so that the ``task`` field cannot
 be empty and the ``dueDate`` field cannot be empty and must be a valid \DateTime

reference/forms/types/collection.rst

@@ -334,7 +334,7 @@ type::
 entry_type
 ~~~~~~~~~~
 
-**type**: ``string`` or :class:`Symfony\\Component\\Form\\FormTypeInterface` **required**
+**type**: ``string`` or :class:`Symfony\\Component\\Form\\FormTypeInterface` **default**: Symfony\\Component\\Form\\Extension\\Core\\Type\\TextType
 
 This is the field type for each item in this collection (e.g. ``TextType``,
 ``ChoiceType``, etc). For example, if you have an array of email addresses,

routing.rst

@@ -576,7 +576,7 @@ Generating URLs with Query Strings
 The ``generate()`` method takes an array of wildcard values to generate the URI.
 But if you pass extra ones, they will be added to the URI as a query string::
 
-    $this->get('router')->generate('blog', array(
+    $this->router->generate('blog', array(
         'page' => 2,
         'category' => 'Symfony'
     ));

service_container.rst

@@ -980,6 +980,8 @@ Learn more
     :maxdepth: 1
     :glob:
 
+    /service_container/*
+
 .. _`service-oriented architecture`: https://en.wikipedia.org/wiki/Service-oriented_architecture
 .. _`Symfony Standard Edition (version 3.3) services.yaml`: https://github.com/symfony/symfony-standard/blob/3.3/app/config/services.yml
 .. _`glob pattern`: https://en.wikipedia.org/wiki/Glob_(programming)