1. Home
  2. Documentation
  3. Service Container
  4. How to Create Service Aliases and Mark Services as Private
WARNING: You are browsing the documentation for Symfony 2.7 which is not maintained anymore. Consider upgrading your projects to Symfony 5.0.

How to Create Service Aliases and Mark Services as Private

2.7 version
Maintained
3.4 4.3 4.4 5.0 current 5.1 master
Unmaintained
2.8 3.0 3.1 3.2 3.3 4.0 4.1 4.2

How to Create Service Aliases and Mark Services as Private

Marking Services as Public / Private

When defining services, you'll usually want to be able to access these definitions within your application code. These services are called public. For example, the doctrine service is a public service. This means that you can fetch it from the container using the get() method:

$doctrine = $container->get('doctrine');

In some cases, a service only exists to be injected into another service and is not intended to be fetched directly from the container as shown above.

In these cases, to get a minor performance boost, you can set the service to be not public (i.e. private):

  • YAML
    1
2
3
4
    services:
    foo:
        class: Example\Foo
        public: false
  • XML
    1
2
3
4
5
6
7
8
9
    <?xml version="1.0" encoding="UTF-8" ?>
<container xmlns="http://symfony.com/schema/dic/services"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd">

    <services>
        <service id="foo" class="Example\Foo" public="false" />
    </services>
</container>
  • PHP
    1
2
3
4
    use Example\Foo;

$container->register('foo', Foo::class)
    ->setPublic(false);

What makes private services special is that, if they are only injected once, they are converted from services to inlined instantiations (e.g. new PrivateThing()). This increases the container's performance.

Now that the service is private, you must not fetch the service directly from the container:

$container->get('foo');

Simply said: A service can be marked as private if you do not want to access it directly from your code.

However, if a service has been marked as private, you can still alias it (see below) to access this service (via the alias).

Note

Services are by default public, but it's considered a good practice to mark as many services private as possible.

Aliasing

You may sometimes want to use shortcuts to access some services. You can do so by aliasing them and, furthermore, you can even alias non-public services.

  • YAML
    1
2
3
4
5
6
    services:
    app.phpmailer:
        class: AppBundle\Mail\PhpMailer

    app.mailer:
        alias: app.phpmailer
  • XML
     1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
    <?xml version="1.0" encoding="UTF-8" ?>
<container xmlns="http://symfony.com/schema/dic/services"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://symfony.com/schema/dic/services
        http://symfony.com/schema/dic/services/services-1.0.xsd">

    <services>
        <service id="app.phpmailer" class="AppBundle\Mail\PhpMailer" />

        <service id="app.mailer" alias="app.phpmailer" />
    </services>
</container>
  • PHP
    1
2
3
4
5
    use AppBundle\Mail\PhpMailer;

$container->register('app.phpmailer', PhpMailer::class);

$container->setAlias('app.mailer', 'app.phpmailer');

This means that when using the container directly, you can access the app.phpmailer service by asking for the app.mailer service like this:

$container->get('app.mailer'); // Would return a PhpMailer instance

Tip

In YAML, you can also use a shortcut to alias a service:

1
2
3
services:
    # ...
    app.mailer: '@app.phpmailer'

This work, including the code samples, is licensed under a Creative Commons BY-SA 3.0 license.