New in Symfony 6.1: Service Decoration Attributes

Contributed by Hubert Lenoir and Robin Chalas in #45834,

46112.

The decorator pattern is a design pattern that allows to modify the behavior of an individual object without affecting the behavior of other objects from the same class. In Symfony applications, service decoration allows you to change the behavior of some service without replacing it or modifying it for other parts of the application. You can already configure service decoration using YAML, XML and PHP. In Symfony 6.1 we're adding the option to configure decoration using PHP attributes. Consider the common case where you want to decorate a service (e.g. Mailer) with a new service that adds logging capabilities to it (e.g. LoggingMailer). This is how you can configure decoration with PHP attributes:

    // src/Mailer/LoggingMailer.php

namespace App\Mailer;

// ... use Symfony\Component\DependencyInjection\Attribute\AsDecorator;

[AsDecorator(decorates: Mailer::class)]

class LoggingMailer { // ... }

The #[AsDecorator] attribute support all the extra options that you might need:

    // ...

[AsDecorator(

decorates: Mailer::class,
priority: 10,
onInvalid: ContainerInterface::IGNORE_ON_INVALID_REFERENCE,

)] class LoggingMailer { // ... }

If you need to access the decorated service inside the decorating one, add the

[MapDecorated] attribute to any of the service constructor arguments:

    // ...

use Symfony\Component\DependencyInjection\Attribute\AsDecorator; use Symfony\Component\DependencyInjection\Attribute\MapDecorated;

[AsDecorator(decorates: Mailer::class)]

class LoggingMailer { public function __construct(#[MapDecorated] Mailer $originalMailer) { // ... }

// ...

}

                Sponsor the Symfony project.

https://symfony.com/blog/new-in-symfony-6-1-service-decoration-attributes?utm_source=Symfony%20Blog%20Feed&utm_medium=feed

Établi 3y | 2 mai 2022 à 09:20:12


Connectez-vous pour ajouter un commentaire

Autres messages de ce groupe

Back on the inspiring SymfonyCon Vienna 2024!

We were absolutely thrilled to gather with the incredible Symfony community for the first time in Vienna, Austria, from December 5th to 6th, surrounded by the warm and festive atmosphere of the

31 janv. 2025 à 12:30:18 | Symfony
SymfonyLive Paris 2025 : Reveal of workshop topics!

SymfonyLive Paris 2025, conference in French language only, will take place from March 27 to 28! The schedule is currently being revealed as we go along. More details are available here.

💻

30 janv. 2025 à 08:50:03 | Symfony
Get Symfony news on your favorite social network

Symfony has been active on X, Mastodon, and Bluesky for some time, but until recently, not all platforms received equal attention. Since Twitter (now X) was our first social network, all blog posts we

29 janv. 2025 à 14:20:10 | Symfony
SymfonyLive Berlin 2025: Demystify the magic of the Container

SymfonyLive Berlin 2025, conference held in English, will take place from April 1 to 4! The schedule is being revealed gradually. More details are available here.

As we are now unveiling th

29 janv. 2025 à 14:20:10 | Symfony
Twig CVE-2025-24374: Missing output escaping for the null coalesce operator

Affected versions

Twig versions >=3.16.0,<3.19.0 are affected by this security issue.

The issue has been fixed in Twig 3.19.0.

Description

When using the null coalesce operator (??), output esc

29 janv. 2025 à 09:40:06 | Symfony
Symfony 6.4.18 released

Symfony 6.4.18 has just been released. Here is the list of the most important changes since 6.4.17:

bug #58889 [Serializer] Handle default context in Serializer (@Valmonzo)

bug #59631 [HttpClient

29 janv. 2025 à 09:40:05 | Symfony
Symfony 7.1.11 released

Symfony 7.1.11 has just been released. Here is the list of the most important changes since 7.1.10:

bug #58889 [Serializer] Handle default context in Serializer (@Valmonzo)

bug #59631 [HttpClient

29 janv. 2025 à 09:40:05 | Symfony