minor #11625 Removed the deprecated factory YAML config (javiereguiluz)

This PR was merged into the 3.4 branch.

Discussion
----------

Removed the deprecated factory YAML config

This backports #11589 to 3.4 so all versions use the same syntax.

Commits
-------

519ccf3 Removed the deprecated factory YAML config

Author: javiereguiluz

service_container/configurators.rst

@@ -136,10 +136,10 @@ all the classes are already loaded as services. All you need to do is specify th
 
             # override the services to set the configurator
             AppBundle\Mail\NewsletterManager:
-                configurator: 'AppBundle\Mail\EmailConfigurator:configure'
+                configurator: ['@AppBundle\Mail\EmailConfigurator', 'configure']
 
             AppBundle\Mail\GreetingCardManager:
-                configurator: 'AppBundle\Mail\EmailConfigurator:configure'
+                configurator: ['@AppBundle\Mail\EmailConfigurator', 'configure']
 
     .. code-block:: xml
 
@@ -184,22 +184,6 @@ all the classes are already loaded as services. All you need to do is specify th
         $container->getDefinition(GreetingCardManager::class)
             ->setConfigurator([new Reference(EmailConfigurator::class), 'configure']);
 
-.. versionadded:: 3.2
-
-    The ``service_id:method_name`` syntax for the YAML configuration format
-    was introduced in Symfony 3.2.
-
-    The traditional configurator syntax in YAML files used an array to define
-    the service id and the method name:
-
-    .. code-block:: yaml
-
-        app.newsletter_manager:
-            # new syntax
-            configurator: 'AppBundle\Mail\EmailConfigurator:configure'
-            # old syntax
-            configurator: ['@AppBundle\Mail\EmailConfigurator', configure]
-
 That's it! When requesting the ``AppBundle\Mail\NewsletterManager`` or
 ``AppBundle\Mail\GreetingCardManager`` service, the created instance will first be
 passed to the ``EmailConfigurator::configure()`` method.

service_container/factories.rst

@@ -41,7 +41,7 @@ configure the service container to use the
 
             AppBundle\Email\NewsletterManager:
                 # call the static method that creates the object
-                factory: ['AppBundle\Email\NewsletterManagerStaticFactory', createNewsletterManager]
+                factory: ['AppBundle\Email\NewsletterManagerStaticFactory', 'createNewsletterManager']
                 # define the class of the created object
                 class: AppBundle\Email\NewsletterManager
 
@@ -107,7 +107,7 @@ Configuration of the service container then looks like this:
 
             AppBundle\Email\NewsletterManager:
                 # call a method on the specified factory service
-                factory: 'AppBundle\Email\NewsletterManagerFactory:createNewsletterManager'
+                factory: ['@AppBundle\Email\NewsletterManagerFactory', 'createNewsletterManager']
                 class: AppBundle\Email\NewsletterManager
 
     .. code-block:: xml
@@ -150,21 +150,6 @@ Configuration of the service container then looks like this:
                 'createNewsletterManager',
             ]);
 
-.. note::
-
-    The traditional configuration syntax in YAML files used an array to define
-    the factory service and the method name:
-
-    .. code-block:: yaml
-
-        # app/config/services.yml
-        AppBundle\Email\NewsletterManager:
-            class: AppBundle\Email\NewsletterManager
-            # new syntax
-            factory: 'AppBundle\Email\NewsletterManagerFactory:createNewsletterManager'
-            # old syntax
-            factory: ['@AppBundle\Email\NewsletterManagerFactory', createNewsletterManager]
-
 .. _factories-passing-arguments-factory-method:
 
 Passing Arguments to the Factory Method