Reword

Author: javiereguiluz

bundles/best_practices.rst

@@ -463,11 +463,6 @@ to the service id. For example, in MonologBundle, an alias is created from
 ``Psr\Log\LoggerInterface`` to ``logger`` so that the ``LoggerInterface`` type-hint
 can be used for autowiring.
 
-.. versionadded:: 4.2
-
-    Since Monolog Bundle 3.5 each channel bind into container by type-hinted alias.
-    More info in the part about :ref:`how to autowire monolog channels <monolog-autowire-channels>`.
-
 Services should not use autowiring or autoconfiguration. Instead, all services should
 be defined explicitly.
 

console/commands_as_services.rst

@@ -53,11 +53,6 @@ the command class will automatically be registered as a service and passed the `
 argument (thanks to autowiring). In other words, *just* by creating this class, everything
 works! You can call the ``app:sunshine`` command and start logging.
 
-.. versionadded:: 4.2
-
-    Since Monolog Bundle 3.5 each channel bind into container by type-hinted alias.
-    More info in the part about :ref:`how to autowire monolog channels <monolog-autowire-channels>`.
-
 .. caution::
 
     You *do* have access to services in ``configure()``. However, if your command is

controller.rst

@@ -275,11 +275,6 @@ the argument by its name:
             ])
         ;
 
-.. versionadded:: 4.2
-
-    Since Monolog Bundle 3.5 each channel bind into container by type-hinted alias.
-    More info in the part about :ref:`how to autowire monolog channels <monolog-autowire-channels>`.
-
 Like with all services, you can also use regular :ref:`constructor injection <services-constructor-injection>`
 in your controllers.
 

logging.rst

@@ -349,15 +349,10 @@ passed as a service.
     was introduced in Symfony 4.2.
 
 If you want to use in your own services a pre-configured logger which uses a
-specific channel (``app`` by default), use the ``monolog.logger`` tag  with the
-``channel`` property as explained in the
+specific channel (``app`` by default), you can either :ref:`autowire monolog channels <monolog-autowire-channels>`
+or use the ``monolog.logger`` tag  with the ``channel`` property as explained in the
 :ref:`Dependency Injection reference <dic_tags-monolog>`.
 
-.. versionadded:: 4.2
-
-    Since Monolog Bundle 3.5 each channel bind into container by type-hinted alias.
-    More info in the part about :ref:`how to autowire monolog channels <monolog-autowire-channels>`.
-
 Adding extra Data to each Log (e.g. a unique request token)
 -----------------------------------------------------------
 

logging/channels_handlers.rst

@@ -14,14 +14,9 @@ the channel).
 
 .. note::
 
-    Each channel corresponds to a logger service (``monolog.logger.XXX``)
-    in the container (use the ``php bin/console debug:container monolog`` command
-    to see a full list) and those are injected into different services.
-
-.. versionadded:: 4.2
-
-    Since Monolog Bundle 3.5 each channel bind into container by type-hinted alias.
-    More info in the part about :ref:`how to autowire monolog channels <monolog-autowire-channels>`.
+    Each channel corresponds to a different logger service (``monolog.logger.XXX``)
+    Use the ``php bin/console debug:container monolog`` command to see a full
+    list of services and learn :ref:`how to autowire monolog channels <monolog-autowire-channels>`.
 
 .. _logging-channel-handler:
 
@@ -180,18 +175,13 @@ inject this service into others, you must update the service configuration to
 
 .. _monolog-autowire-channels:
 
-How to autowire logger channels
+How to Autowire Logger Channels
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 4.2
-
-    This feature available since MonologBundle 3.5
-
-Each channel already bind into container by type-hinted alias.
-Just use method variables, which follows next naming template ``Psr\Log\LoggerInterface $<channel>Logger``.
-For example, you have ``App\Log\CustomLogger`` service which tagged by ``app`` logger channel
-as described in part :ref:`Logging with a custom logging channel <dic_tags-monolog>`.
-Now you can remove service configuration at all and change constructor signature:
+Starting from `MonologBundle`_ 3.5 you can autowire different Monolog channels
+by type-hinting your service arguments with the following syntax:
+``Psr\Log\LoggerInterface $<channel>Logger``. For example, to inject the service
+related to the ``app`` logger channel use this:
 
 .. code-block:: diff
 
@@ -200,3 +190,5 @@ Now you can remove service configuration at all and change constructor signature
         {
             $this->logger = $appLogger;
         }
+
+.. _`MonologBundle`: https://github.com/symfony/monolog-bundle

quick_tour/the_architecture.rst

@@ -52,11 +52,6 @@ But wait! Something *very* cool just happened. Symfony read the ``LoggerInterfac
 type-hint and automatically figured out that it should pass us the Logger object!
 This is called *autowiring*.
 
-.. versionadded:: 4.2
-
-    Furthermore, since Monolog Bundle 3.5 each channel bind into container by type-hinted alias.
-    More info in the part about :ref:`how to autowire monolog channels <monolog-autowire-channels>`.
-
 Every bit of work that's done in a Symfony app is done by an *object*: the Logger
 object logs things and the Twig object renders templates. These objects are called
 *services* and they are *tools* that help you build rich features.

reference/configuration/monolog.rst

@@ -8,11 +8,6 @@ The MonologBundle integrates the Monolog :doc:`logging </logging>` library in
 Symfony applications. All these options are configured under the ``monolog`` key
 in your application configuration.
 
-.. versionadded:: 4.2
-
-    Since Monolog Bundle 3.5 each channel bind into container by type-hinted alias.
-    More info in the part about :ref:`how to autowire monolog channels <monolog-autowire-channels>`.
-
 .. code-block:: terminal
 
     # displays the default config values defined by Symfony

reference/dic_tags.rst

@@ -530,14 +530,8 @@ channel when injecting the logger in a service.
 
 .. tip::
 
-    You can also configure custom channels in the configuration and retrieve
-    the corresponding logger service from the service container directly (see
-    :ref:`monolog-channels-config`).
-
-.. versionadded:: 4.2
-
-    Since Monolog Bundle 3.5 each channel bind into container by type-hinted alias.
-    More info in the part about :ref:`how to autowire monolog channels <monolog-autowire-channels>`.
+    You can create :doc:`custom channels </logging/channels_handlers>` and
+    even :ref:`autowire logging channels <monolog-autowire-channels>`.
 
 .. _dic_tags-monolog-processor:
 

service_container.rst

@@ -616,13 +616,6 @@ But, you can control this and pass in a different logger:
 This tells the container that the ``$logger`` argument to ``__construct`` should use
 service whose id is ``monolog.logger.request``.
 
-.. versionadded:: 4.2
-
-    Since Monolog Bundle 3.5 each channel already into container by type-hinted alias.
-    Instead of explicit declare configuration ``$logger: '@monolog.logger.request'``
-    just use variable in the constructor signature: ``Psr\Log\LoggerInterface $requestLogger``.
-    More info in the part about :ref:`how to autowire monolog channels <monolog-autowire-channels>`.
-
 .. _container-debug-container:
 
 For a full list of *all* possible services in the container, run:
@@ -721,11 +714,6 @@ argument for *any* service defined in this file! You can bind arguments by name
 (e.g. ``$adminEmail``), by type (e.g. ``Psr\Log\LoggerInterface``) or both
 (e.g. ``Psr\Log\LoggerInterface $requestLogger``).
 
-.. versionadded:: 4.2
-
-    Since Monolog Bundle 3.5 each channel already bind into container by type-hinted alias.
-    More info in the part about :ref:`how to autowire monolog channels <monolog-autowire-channels>`.
-
 The ``bind`` config can also be applied to specific services or when loading many
 services at once (i.e. :ref:`service-psr4-loader`).
 

service_container/3.3-di-changes.rst

@@ -392,13 +392,8 @@ create the class::
     }
 
 Great! In Symfony 3.2 or lower, you would now need to register this as a service
-in ``services.yaml`` and tag it with ``kernel.event_subscriber``.
-In Symfony 3.3, you're already done!
-
-.. versionadded:: 4.2
-
-    Furthermore, since Monolog Bundle 3.5 each channel bind into container by type-hinted alias.
-    More info in the part about :ref:`how to autowire monolog channels <monolog-autowire-channels>`.
+in ``services.yaml`` and tag it with ``kernel.event_subscriber``. In Symfony 3.3,
+you're already done!
 
 The service is :ref:`automatically registered <service-33-changes-automatic-registration>`.
 And thanks to ``autoconfigure``, Symfony automatically tags the service because