Update some examples using 3.3 features

Author: GuilhemN

best_practices/templates.rst

@@ -73,18 +73,8 @@ a new dependency of the project:
 
     $ composer require erusev/parsedown
 
-Then, create a new ``Markdown`` service that will be used later by the Twig
-extension. The service definition only requires the path to the class:
-
-.. code-block:: yaml
-
-    # app/config/services.yml
-    services:
-        # ...
-        app.markdown:
-            class: AppBundle\Utils\Markdown
-
-And the ``Markdown`` class just needs to define one single method to transform
+Then, create a new ``Markdown`` class that will be used later by the Twig
+extension. It just needs to define one single method to transform
 Markdown content into HTML::
 
     namespace AppBundle\Utils;
@@ -147,17 +137,36 @@ service in the constructor of the Twig extension:
         }
     }
 
-Lastly define a new service to enable this Twig extension in the app (the service
-name is irrelevant because you never use it in your own code):
+Lastly make sure these new classes are registered as services:
 
 .. code-block:: yaml
 
     # app/config/services.yml
     services:
-        app.twig.app_extension:
-            class:     AppBundle\Twig\AppExtension
+        # default configuration for services in *this* file
+        _defaults:
+            autowire: true
+            autoconfigure: true
+            public: false
+
+        # loads services from whatever directories you want (you can update this!)
+        AppBundle\:
+            resource: '../../src/AppBundle/{Twig,Utils}'
+
+Or if you want to register them explicitly:
+
+.. code-block:: yaml
+
+    # app/config/services.yml
+    services:
+        _defaults:
+            public: false
+
+        app.markdown:
+            class: AppBundle\Utils\Markdown
+
+        AppBundle\Twig\AppExtension:
             arguments: ['@app.markdown']
-            public:    false
             tags: [twig.extension]
 
 .. _`Twig`: http://twig.sensiolabs.org/

console/commands_as_services.rst

@@ -27,9 +27,7 @@ with ``console.command``:
 
         # app/config/config.yml
         services:
-            app.command.my_command:
-                class: AppBundle\Command\MyCommand
-                tags: [console.command]
+            AppBundle\Command\MyCommand: [console.command]
 
     .. code-block:: xml
 
@@ -41,8 +39,7 @@ with ``console.command``:
             http://symfony.com/schema/dic/services/services-1.0.xsd">
 
             <services>
-                <service id="app.command.my_command"
-                    class="AppBundle\Command\MyCommand">
+                <service id="AppBundle\Command\MyCommand">
                     <tag name="console.command" />
                 </service>
             </services>
@@ -54,7 +51,7 @@ with ``console.command``:
         use AppBundle\Command\MyCommand;
 
         $container
-            ->register('app.command.my_command', MyCommand::class)
+            ->register(MyCommand::class)
             ->addTag('console.command')
         ;
 
@@ -131,8 +128,7 @@ inject the ``command.default_name`` parameter:
             command.default_name: Javier
 
         services:
-            app.command.my_command:
-                class: AppBundle\Command\MyCommand
+            AppBundle\Command\MyCommand:
                 arguments: ["%command.default_name%"]
                 tags: [console.command]
 
@@ -150,8 +146,7 @@ inject the ``command.default_name`` parameter:
             </parameters>
 
             <services>
-                <service id="app.command.my_command"
-                    class="AppBundle\Command\MyCommand">
+                <service class="AppBundle\Command\MyCommand">
                     <argument>%command.default_name%</argument>
                     <tag name="console.command" />
                 </service>
@@ -166,7 +161,7 @@ inject the ``command.default_name`` parameter:
         $container->setParameter('command.default_name', 'Javier');
 
         $container
-            ->register('app.command.my_command', MyCommand::class)
+            ->register(MyCommand::class)
             ->setArguments(array('%command.default_name%'))
             ->addTag('console.command')
         ;

controller/argument_value_resolver.rst

@@ -146,8 +146,7 @@ and adding a priority.
 
         # app/config/services.yml
         services:
-            app.value_resolver.user:
-                class: AppBundle\ArgumentResolver\UserValueResolver
+            AppBundle\ArgumentResolver\UserValueResolver:
                 arguments:
                     - '@security.token_storage'
                 tags:
@@ -162,10 +161,8 @@ and adding a priority.
             xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
 
             <services>
-                <service id="app.value_resolver.user"
-                    class="AppBundle\ArgumentResolver\UserValueResolver"
-                >
-                    <argument type="service" id="security.token_storage">
+                <service id="AppBundle\ArgumentResolver\UserValueResolver">
+                    <argument type="service" id="security.token_storage" />
                     <tag name="controller.argument_value_resolver" priority="50" />
                 </service>
             </services>
@@ -175,14 +172,12 @@ and adding a priority.
     .. code-block:: php
 
         // app/config/services.php
+        use AppBundle\ArgumentResolver\UserValueResolver;
         use Symfony\Component\DependencyInjection\Definition;
 
-        $definition = new Definition(
-            'AppBundle\ArgumentResolver\UserValueResolver',
-            array(new Reference('security.token_storage'))
-        );
-        $definition->addTag('controller.argument_value_resolver', array('priority' => 50));
-        $container->setDefinition('app.value_resolver.user', $definition);
+        $container->register(UserValueResolver::class)
+            ->addArgument(new Reference('security.token_storage'))
+            ->addTag('controller.argument_value_resolver', array('priority' => 50));
 
 While adding a priority is optional, it's recommended to add one to make sure
 the expected value is injected. The ``RequestAttributeValueResolver`` has a

controller/error_pages.rst

@@ -269,8 +269,7 @@ In that case, you might want to override one or both of the ``showAction()`` and
 
             # app/config/services.yml
             services:
-                app.exception_controller:
-                    class: AppBundle\Controller\CustomExceptionController
+                AppBundle\Controller\CustomExceptionController:
                     arguments: ['@twig', '%kernel.debug%']
 
         .. code-block:: xml
@@ -282,9 +281,7 @@ In that case, you might want to override one or both of the ``showAction()`` and
                 xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd"
             >
                 <services>
-                    <service id="app.exception_controller"
-                        class="AppBundle\Controller\CustomExceptionController"
-                    >
+                    <service id="AppBundle\Controller\CustomExceptionController">
                         <argument type="service" id="twig"/>
                         <argument>%kernel.debug%</argument>
                     </service>
@@ -297,14 +294,14 @@ In that case, you might want to override one or both of the ``showAction()`` and
             use AppBundle\Controller\CustomExceptionController;
             use Symfony\Component\DependencyInjection\Reference;
 
-            $container->register('app.exception_controller', CustomExceptionController::class)
+            $container->register(CustomExceptionController::class)
                 ->setArguments(array(
                     new Reference('twig'),
                     '%kernel.debug%',
                 ));
 
-    And then configure ``twig.exception_controller`` using the controller as
-    services syntax (e.g. ``app.exception_controller:showAction``).
+    And then configure ``twig.exception_controller`` to point to this service
+    (using ``AppBundle:CustomException:showAction`` for example).
 
 .. tip::
 

doctrine/event_listeners_subscribers.rst

@@ -41,16 +41,13 @@ managers that use this connection.
                         memory: true
 
         services:
-            my.listener:
-                class: AppBundle\EventListener\SearchIndexer
+            AppBundle\EventListener\SearchIndexer:
                 tags:
                     - { name: doctrine.event_listener, event: postPersist }
-            my.listener2:
-                class: AppBundle\EventListener\SearchIndexer2
+            AppBundle\EventListener\SearchIndexer2:
                 tags:
                     - { name: doctrine.event_listener, event: postPersist, connection: default }
-            my.subscriber:
-                class: AppBundle\EventListener\SearchIndexerSubscriber
+            AppBundle\EventListener\SearchIndexerSubscriber:
                 tags:
                     - { name: doctrine.event_subscriber, connection: default }
 
@@ -67,13 +64,13 @@ managers that use this connection.
             </doctrine:config>
 
             <services>
-                <service id="my.listener" class="AppBundle\EventListener\SearchIndexer">
+                <service id="AppBundle\EventListener\SearchIndexer">
                     <tag name="doctrine.event_listener" event="postPersist" />
                 </service>
-                <service id="my.listener2" class="AppBundle\EventListener\SearchIndexer2">
+                <service id="AppBundle\EventListener\SearchIndexer2">
                     <tag name="doctrine.event_listener" event="postPersist" connection="default" />
                 </service>
-                <service id="my.subscriber" class="AppBundle\EventListener\SearchIndexerSubscriber">
+                <service id="AppBundle\EventListener\SearchIndexerSubscriber">
                     <tag name="doctrine.event_subscriber" connection="default" />
                 </service>
             </services>
@@ -97,28 +94,25 @@ managers that use this connection.
             ),
         ));
 
-        $container
-            ->register('my.listener', SearchIndexer::class)
+        $container->register(SearchIndexer::class)
             ->addTag('doctrine.event_listener', array('event' => 'postPersist'))
         ;
-        $container
-            ->register('my.listener2', SearchIndexer2::class)
+        $container->register(SearchIndexer2::class)
             ->addTag('doctrine.event_listener', array(
                 'event' => 'postPersist',
                 'connection' => 'default'
             ))
         ;
-        $container
-            ->register('my.subscriber', SearchIndexerSubscriber::class)
+        $container->register(SearchIndexerSubscriber::class)
             ->addTag('doctrine.event_subscriber', array('connection' => 'default'))
         ;
 
 Creating the Listener Class
 ---------------------------
 
-In the previous example, a service ``my.listener`` was configured as a Doctrine
-listener on the event ``postPersist``. The class behind that service must have
-a ``postPersist()`` method, which will be called when the event is dispatched::
+In the previous example, the ``SearchIndexer`` class was configured as a
+Doctrine listener on the event ``postPersist``. So it must have a
+``postPersist()`` method, which will be called when the event is dispatched::
 
     // src/AppBundle/EventListener/SearchIndexer.php
     namespace AppBundle\EventListener;

event_dispatcher.rst

@@ -77,8 +77,7 @@ using a special "tag":
 
         # app/config/services.yml
         services:
-            app.exception_listener:
-                class: AppBundle\EventListener\ExceptionListener
+            AppBundle\EventListener\ExceptionListener:
                 tags:
                     - { name: kernel.event_listener, event: kernel.exception }
 
@@ -91,9 +90,7 @@ using a special "tag":
             xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
 
             <services>
-                <service id="app.exception_listener"
-                    class="AppBundle\EventListener\ExceptionListener">
-
+                <service id="AppBundle\EventListener\ExceptionListener">
                     <tag name="kernel.event_listener" event="kernel.exception" />
                 </service>
             </services>
@@ -105,7 +102,7 @@ using a special "tag":
         use AppBundle\EventListener\ExceptionListener;
 
         $container
-            ->register('app.exception_listener', ExceptionListener::class)
+            ->register(ExceptionListener::class)
             ->addTag('kernel.event_listener', array('event' => 'kernel.exception'))
         ;
 
@@ -185,10 +182,7 @@ Now, you just need to register the class as a service and add the
 
         # app/config/services.yml
         services:
-            app.exception_subscriber:
-                class: AppBundle\EventSubscriber\ExceptionSubscriber
-                tags:
-                    - { name: kernel.event_subscriber }
+            AppBundle\EventSubscriber\ExceptionSubscriber: [kernel.event_subscriber]
 
     .. code-block:: xml
 
@@ -199,9 +193,7 @@ Now, you just need to register the class as a service and add the
             xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">
 
             <services>
-                <service id="app.exception_subscriber"
-                    class="AppBundle\EventSubscriber\ExceptionSubscriber">
-
+                <service id="AppBundle\EventSubscriber\ExceptionSubscriber">
                     <tag name="kernel.event_subscriber"/>
                 </service>
             </services>
@@ -213,7 +205,7 @@ Now, you just need to register the class as a service and add the
         use AppBundle\EventSubscriber\ExceptionSubscriber;
 
         $container
-            ->register('app.exception_subscriber', ExceptionSubscriber::class)
+            ->register(ExceptionSubscriber::class)
             ->addTag('kernel.event_subscriber')
         ;