Merge remote-tracking branch 'origin/master' into di-3.3-changes

* origin/master: (36 commits)
  Use the short Yaml syntax for service definition
  [#7613] remove reference to AsseticBundle
  minor #7613 Twig Extensions Reference minor brush-up (mpdude)
  Fix service locator declaration
  Minor reword
  Update Title in controller.rst
  Update scheme.rst
  Update requirements.rst
  [3.3] Document FQCN named controllers
  Document FQCN named controllers
  Use the short tag syntax
  [#7845] minor tweaks
  Update translation_domain.rst.inc
  Update page_creation.rst to correct hidden colon
  Update forms.rst
  Rewords
  Fixed the form types of the buttons in the Form reference
  [#7832] use bin/console for Symfony 3.x
  Minor reword
  Update deployment.rst
  ...

Author: weaverryan

best_practices/security.rst

@@ -339,8 +339,7 @@ To enable the security voter in the application, define a new service:
             class:      AppBundle\Security\PostVoter
             arguments: ['@security.access.decision_manager']
             public:     false
-            tags:
-               - { name: security.voter }
+            tags: [security.voter]
 
 Now, you can use the voter with the ``@Security`` annotation:
 

best_practices/templates.rst

@@ -158,8 +158,7 @@ name is irrelevant because you never use it in your own code):
             class:     AppBundle\Twig\AppExtension
             arguments: ['@app.markdown']
             public:    false
-            tags:
-                - { name: twig.extension }
+            tags: [twig.extension]
 
 .. _`Twig`: http://twig.sensiolabs.org/
 .. _`Parsedown`: http://parsedown.org/

components/cache/cache_pools.rst

@@ -9,6 +9,8 @@
     single: PDO Cache, Doctrine DBAL Cache
     single: Redis Cache
 
+.. _component-cache-cache-pools:
+
 Cache Pools and Supported Adapters
 ==================================
 

components/phpunit_bridge.rst

@@ -208,7 +208,7 @@ If you have this kind of time-related tests::
 
 You used the :doc:`Symfony Stopwatch Component </components/stopwatch>` to
 calculate the duration time of your process, here 10 seconds. However, depending
-on the load of the server your the processes running on your local machine, the
+on the load of the server or the processes running on your local machine, the
 ``$duration`` could for example be `10.000023s` instead of `10s`.
 
 This kind of tests are called transient tests: they are failing randomly
@@ -390,7 +390,7 @@ Modified PHPUnit script
 -----------------------
 
 .. versionadded:: 3.2
-    The modified PHPUnit script script was introduced in the 3.2 version of 
+    This modified PHPUnit script was introduced in the 3.2 version of 
     this component.
 
 This bridge provides a modified version of PHPUnit that you can call by using
@@ -423,8 +423,8 @@ If you have installed the bridge through Composer, you can run it by calling e.g
 
 .. tip::
 
-    Set the ``SYMFONY_PHPUNIT_REMOVE`` env var to ``symfony/yaml`` if you need
-    ``prophecy`` but not ``symfony/yaml``.
+    If you still need to use ``prophecy`` (but not ``symfony/yaml``), 
+    then set the ``SYMFONY_PHPUNIT_REMOVE`` env var to ``symfony/yaml``.
 
 .. _PHPUnit: https://phpunit.de
 .. _`PHPUnit event listener`: https://phpunit.de/manual/current/en/extending-phpunit.html#extending-phpunit.PHPUnit_Framework_TestListener

console.rst

@@ -273,7 +273,7 @@ you can extend your test from
     {
         public function testExecute()
         {
-            $kernel = $this->createKernel();
+            $kernel = static::createKernel();
             $kernel->boot();
 
             $application = new Application($kernel);

console/commands_as_services.rst

@@ -29,8 +29,7 @@ with ``console.command``:
         services:
             app.command.my_command:
                 class: AppBundle\Command\MyCommand
-                tags:
-                    - { name: console.command }
+                tags: [console.command]
 
     .. code-block:: xml
 
@@ -89,7 +88,7 @@ store the default value in some ``%command.default_name%`` parameter::
         public function __construct($defaultName)
         {
             $this->defaultName = $defaultName;
-            
+
             parent::__construct();
         }
 
@@ -135,8 +134,7 @@ inject the ``command.default_name`` parameter:
             app.command.my_command:
                 class: AppBundle\Command\MyCommand
                 arguments: ["%command.default_name%"]
-                tags:
-                    - { name: console.command }
+                tags: [console.command]
 
     .. code-block:: xml
 

contributing/code/tests.rst

@@ -55,6 +55,6 @@ what's going on and if the tests are broken because of the new code.
     to see colored test results.
 
 .. _Cmder: http://cmder.net/
-.. _ConEmu: https://code.google.com/p/conemu-maximus5/
+.. _ConEmu: https://conemu.github.io/
 .. _ANSICON: https://github.com/adoxa/ansicon/releases
 .. _Mintty: https://mintty.github.io/

controller.rst

@@ -236,6 +236,7 @@ The Symfony templating system and Twig are explained more in the
    single: Controller; Accessing services
 
 .. _controller-accessing-services:
+.. _accessing-other-services:
 
 Fetching Services as Arguments
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

controller/service.rst

@@ -66,36 +66,36 @@ Then you can define it as a service as follows:
 
         # app/config/services.yml
         services:
-            app.hello_controller:
-                class: AppBundle\Controller\HelloController
+            AppBundle\Controller\HelloController: ~
 
     .. code-block:: xml
 
         <!-- app/config/services.xml -->
         <services>
-            <service id="app.hello_controller" class="AppBundle\Controller\HelloController" />
+            <service id="AppBundle\Controller\HelloController" />
         </services>
 
     .. code-block:: php
 
         // app/config/services.php
         use AppBundle\Controller\HelloController;
 
-        $container->register('app.hello_controller', HelloController::class);
+        $container->register(HelloController::class);
 
 Referring to the Service
 ------------------------
 
-To refer to a controller that's defined as a service, use the single colon (:)
-notation. For example, to forward to the ``indexAction()`` method of the service
-defined above with the id ``app.hello_controller``::
+If the service id is the fully-qualified class name (FQCN) of your controller,
+you can keep using the usual notation. For example, to forward to the
+``indexAction()`` method of the above ``AppBundle\Controller\HelloController``
+service::
 
-    $this->forward('app.hello_controller:indexAction', array('name' => $name));
+    $this->forward('AppBundle:Hello:index', array('name' => $name));
 
-.. note::
+Otherwise, use the single colon (``:``) notation. For example, to forward to the
+``indexAction()`` method of a service with the id ``app.hello_controller``::
 
-    You cannot drop the ``Action`` part of the method name when using this
-    syntax.
+    $this->forward('app.hello_controller:indexAction', array('name' => $name));
 
 You can also route to the service by using the same notation when defining
 the route ``_controller`` value:
@@ -123,17 +123,24 @@ the route ``_controller`` value:
             '_controller' => 'app.hello_controller:indexAction',
         )));
 
+.. note::
+
+    You cannot drop the ``Action`` part of the method name when using the
+    single colon notation.
+
 .. tip::
 
     You can also use annotations to configure routing using a controller
     defined as a service. Make sure you specify the service ID in the
-    ``@Route`` annotation. See the `FrameworkExtraBundle documentation`_ for
-    details.
+    ``@Route`` annotation if your service ID is not your controller
+    fully-qualified class name (FQCN). See the
+    `FrameworkExtraBundle documentation`_ for details.
 
 .. tip::
 
     If your controller implements the ``__invoke()`` method, you can simply
-    refer to the service id (``app.hello_controller``).
+    refer to the service id (``AppBundle\Controller\HelloController`` or
+    ``app.hello_controller`` for example).
 
 Alternatives to base Controller Methods
 ---------------------------------------
@@ -209,15 +216,14 @@ argument:
 
         # app/config/services.yml
         services:
-            app.hello_controller:
-                class:     AppBundle\Controller\HelloController
+            AppBundle\Controller\HelloController:
                 arguments: ['@templating']
 
     .. code-block:: xml
 
         <!-- app/config/services.xml -->
         <services>
-            <service id="app.hello_controller" class="AppBundle\Controller\HelloController">
+            <service id="AppBundle\Controller\HelloController">
                 <argument type="service" id="templating"/>
             </service>
         </services>
@@ -226,13 +232,10 @@ argument:
 
         // app/config/services.php
         use AppBundle\Controller\HelloController;
-        use Symfony\Component\DependencyInjection\Definition;
         use Symfony\Component\DependencyInjection\Reference;
 
-        $container->setDefinition('app.hello_controller', new Definition(
-            HelloController::class,
-            array(new Reference('templating'))
-        ));
+        $container->register(HelloController::class)
+            ->addArgument(new Reference('templating'));
 
 Rather than fetching the ``templating`` service from the container, you can
 inject *only* the exact service(s) that you need directly into the controller.

deployment.rst

@@ -80,7 +80,7 @@ specifically tailored to the requirements of Symfony.
 `Capistrano`_ with `Symfony plugin`_
     `Capistrano`_ is a remote server automation and deployment tool written in Ruby.
     `Symfony plugin`_ is a plugin to ease Symfony related tasks, inspired by `Capifony`_
-    (which works only with Capistrano 2 )
+    (which works only with Capistrano 2).
 
 `sf2debpkg`_
     Helps you build a native Debian package for your Symfony project.
@@ -182,12 +182,12 @@ setup:
 * Pushing assets to a CDN
 * ...
 
-Application Lifecycle: Continuous Integration, QA, etc
-------------------------------------------------------
+Application Lifecycle: Continuous Integration, QA, etc.
+-------------------------------------------------------
 
 While this entry covers the technical details of deploying, the full lifecycle
-of taking code from development up to production may have a lot more steps
-(think deploying to staging, QA (Quality Assurance), running tests, etc).
+of taking code from development up to production may have more steps:
+deploying to staging, QA (Quality Assurance), running tests, etc.
 
 The use of staging, testing, QA, continuous integration, database migrations
 and the capability to roll back in case of failure are all strongly advised. There