Linting Service Definitions

The ``lint:container`` command performs some additional checks to make sure

the container is properly configured:

* ensures the arguments injected into services match their type declarations.

* ensures the interfaces configured as alias are resolving to a compatible

service.

It's useful to run it before deploying your application to production

(e.g. in your continuous integration server):

The ``lint:container`` command performs additional checks to ensure the container

is properly configured. It is useful to run this command before deploying your

application to production (e.g. in your continuous integration server):

..code-block::terminal

Doing those checks whenever the container is compiled

can hurt performance. That's why this is implemented in

:doc:`compiler passes</service_container/compiler_passes>` called

``CheckTypeDeclarationsPass`` and ``CheckAliasValidityPass`` which are disabled

by default and enabled only when executing the ``lint:container`` command.

If you don't mind the performance loss, enable these compiler passes in

Performing those checks whenever the container is compiled can hurt performance.

That's why they are implemented in:doc:`compiler passes</service_container/compiler_passes>`

called ``CheckTypeDeclarationsPass`` and ``CheckAliasValidityPass``, which are

disabled by default and enabled only when executing the ``lint:container`` command.

If you don't mind the performance loss, you can enable these compiler passes in

your application.

..versionadded::7.1

The ``CheckAliasValidityPass`` compiler pass was introduced in Symfony 7.1.

.. _container-public:

Public Versus Private Services