Sep 23, 2019 · Sep 24, 2018 · Oct 8, 2018 · Feb 23, 2019
diff --git a/service_container/service_subscribers_locators.rst b/service_container/service_subscribers_locators.rst
 --------------------------

 To manually define a service locator, create a new service definition and add
 the ``container.service_locator`` tag to it. Useits ``arguments`` option to
 include as manyservicesas needed in it.
 the ``container.service_locator`` tag to it. Usethe first argument of the
 service definition to pass a collection ofservicesto the service locator:

 .. configuration-block::

                    -
                        App\FooCommand: '@app.command_handler.foo'
                        App\BarCommand: '@app.command_handler.bar'
                        # if the element has no key, the ID of the original service is used
                        '@app.command_handler.baz'

                # if you are not using the default service autoconfiguration,
                # add the following tag to the service definition:
                # tags: ['container.service_locator']

                <service id="app.command_handler_locator" class="Symfony\Component\DependencyInjection\ServiceLocator">
                    <argument type="collection">
                        <argument key="App\FooCommand" type="service" id="app.command_handler.foo"/>
                        <argument key="App\BarCommand" type="service" id="app.command_handler.bar"/>
                        <argument key="App\FooCommand" type="service" id="app.command_handler.foo" />
                        <argument key="App\BarCommand" type="service" id="app.command_handler.bar" />
                        <!-- if the element has no key, the ID of the original service is used -->
                        <argument type="service" id="app.command_handler.baz" />
                    </argument>
                    <!--
                        if you are not using the default service autoconfiguration,
            ->setArguments([[
                'App\FooCommand' => new Reference('app.command_handler.foo'),
                'App\BarCommand' => new Reference('app.command_handler.bar'),
            ]])
                // if the element has no key, the ID of the original service is used
                new Reference('app.command_handler.baz'),
            )))
            // if you are not using the default service autoconfiguration,
            // add the following tag to the service definition:
            // ->addTag('container.service_locator')
        ;

 .. versionadded:: 4.1
    The service locator autoconfiguration was introduced in Symfony 4.1. In
    previous Symfony versions you always needed to add the
    ``container.service_locator`` tag explicitly.

 .. versionadded:: 4.2

    The ability to add services without specifying their id was introduced in
    Symfony 4.2.

 .. note::

    The services defined in the service locator argument must include keys,
Original file line number	Diff line number	Diff line change
Expand Up		@@ -243,8 +243,8 @@ Defining a Service Locator
		--------------------------

		To manually define a service locator, create a new service definition and add
		the ``container.service_locator`` tag to it. Useits ``arguments`` option to
		include as manyservicesas needed in it.
		the ``container.service_locator`` tag to it. Usethe first argument of the
		service definition to pass a collection ofservicesto the service locator:

		.. configuration-block::

Expand All		@@ -258,6 +258,9 @@ include as many services as needed in it.
		-
		App\FooCommand: '@app.command_handler.foo'
		App\BarCommand: '@app.command_handler.bar'
		# if the element has no key, the ID of the original service is used
		'@app.command_handler.baz'

		# if you are not using the default service autoconfiguration,
		# add the following tag to the service definition:
		# tags: ['container.service_locator']
Expand All		@@ -274,8 +277,10 @@ include as many services as needed in it.

		<service id="app.command_handler_locator" class="Symfony\Component\DependencyInjection\ServiceLocator">
		<argument type="collection">
		<argument key="App\FooCommand" type="service" id="app.command_handler.foo"/>
		<argument key="App\BarCommand" type="service" id="app.command_handler.bar"/>
		<argument key="App\FooCommand" type="service" id="app.command_handler.foo" />
		<argument key="App\BarCommand" type="service" id="app.command_handler.bar" />
		<!-- if the element has no key, the ID of the original service is used -->
		<argument type="service" id="app.command_handler.baz" />
		</argument>
		<!--
		if you are not using the default service autoconfiguration,
Expand All		@@ -300,12 +305,24 @@ include as many services as needed in it.
		->setArguments([[
		'App\FooCommand' => new Reference('app.command_handler.foo'),
		'App\BarCommand' => new Reference('app.command_handler.bar'),
		]])
		// if the element has no key, the ID of the original service is used
		new Reference('app.command_handler.baz'),
		)))
		// if you are not using the default service autoconfiguration,
		// add the following tag to the service definition:
		// ->addTag('container.service_locator')
		;

		.. versionadded:: 4.1
		The service locator autoconfiguration was introduced in Symfony 4.1. In
		previous Symfony versions you always needed to add the
		``container.service_locator`` tag explicitly.

		.. versionadded:: 4.2
Copy link Contributor OskarStarkFeb 23, 2019 Choose a reason for hiding this comment The reason will be displayed to describe this comment to others.Learn more. Please add a blank line after the directive

		The ability to add services without specifying their id was introduced in
		Symfony 4.2.

		.. note::

		The services defined in the service locator argument must include keys,
Expand Down