Jan 23, 2023 · Jan 21, 2023
diff --git a/service_container/lazy_services.rst b/service_container/lazy_services.rst

    $ composer require symfony/proxy-manager-bridge

 .. _lazy-services_configuration:

 Configuration
 -------------

    over the ``lazy`` flag and directly instantiate the service as it would
    normally do.

 You can also configure your service's laziness thanks to the
 :class:`Symfony\\Component\\DependencyInjection\\Attribute\\Autoconfigure` attribute.
 The attribute has to be used like this::

    namespace App\Twig;

    use Symfony\Component\DependencyInjection\Attribute\Autoconfigure;
    use Twig\Extension\ExtensionInterface;

    #[Autoconfigure(lazy: true)]
    class AppExtension implements ExtensionInterface
    {
        // ...
    }

 .. versionadded:: 5.4

    The :class:`Symfony\\Component\\DependencyInjection\\Attribute\\Autoconfigure` attribute
    was introduced in Symfony 5.4.

 Interface Proxifying
 --------------------

            ;
        };

 Just like in the :ref:`Configuration <lazy-services_configuration>` section, you can
 use the :class:`Symfony\\Component\\DependencyInjection\\Attribute\\Autoconfigure`
 attribute to configure the interface to proxify by passing its FQCN as the ``lazy``
 parameter value::

    namespace App\Twig;

    use Symfony\Component\DependencyInjection\Attribute\Autoconfigure;
    use Twig\Extension\ExtensionInterface;

    #[Autoconfigure(lazy: ExtensionInterface::class)]
    class AppExtension implements ExtensionInterface
    {
        // ...
    }

 .. versionadded:: 5.4

    The :class:`Symfony\\Component\\DependencyInjection\\Attribute\\Autoconfigure` attribute
    was introduced in Symfony 5.4.

 The virtual `proxy`_ injected into other services will only implement the
 specified interfaces and will not extend the original service class, allowing to
 lazy load services using `final`_ classes. You can configure the proxy to
Original file line number	Diff line number	Diff line change
Expand Up		@@ -41,6 +41,8 @@ In order to use the lazy service instantiation, you will need to install the

		$ composer require symfony/proxy-manager-bridge

		.. _lazy-services_configuration:

		Configuration
		-------------

Expand DownExpand Up		@@ -101,6 +103,26 @@ To check if your proxy works you can check the interface of the received object:
		over the ``lazy`` flag and directly instantiate the service as it would
		normally do.

		You can also configure your service's laziness thanks to the
		:class:`Symfony\\Component\\DependencyInjection\\Attribute\\Autoconfigure` attribute.
		The attribute has to be used like this::

		namespace App\Twig;

		use Symfony\Component\DependencyInjection\Attribute\Autoconfigure;
		use Twig\Extension\ExtensionInterface;

		#[Autoconfigure(lazy: true)]
		class AppExtension implements ExtensionInterface
		{
		// ...
		}

		.. versionadded:: 5.4

		The :class:`Symfony\\Component\\DependencyInjection\\Attribute\\Autoconfigure` attribute
		was introduced in Symfony 5.4.

		Interface Proxifying
		--------------------

Expand DownExpand Up		@@ -159,6 +181,27 @@ specific interfaces.
		;
		};

		Just like in the :ref:`Configuration <lazy-services_configuration>` section, you can
		use the :class:`Symfony\\Component\\DependencyInjection\\Attribute\\Autoconfigure`
		attribute to configure the interface to proxify by passing its FQCN as the ``lazy``
		parameter value::

		namespace App\Twig;

		use Symfony\Component\DependencyInjection\Attribute\Autoconfigure;
		use Twig\Extension\ExtensionInterface;

		#[Autoconfigure(lazy: ExtensionInterface::class)]
		class AppExtension implements ExtensionInterface
		{
		// ...
		}

		.. versionadded:: 5.4

		The :class:`Symfony\\Component\\DependencyInjection\\Attribute\\Autoconfigure` attribute
		was introduced in Symfony 5.4.

		The virtual `proxy`_ injected into other services will only implement the
		specified interfaces and will not extend the original service class, allowing to
		lazy load services using `final`_ classes. You can configure the proxy to
Expand Down