Creating a New Mailer, Notifier or Translation Bridge

Update the Code

• Add the new bridge to the UnsupportedSchemeException class of the component and to its UnsupportedSchemeExceptionTest test class;
• For Mailer and Notifier bridges, add the new transport factory to the FACTORY_CLASSES constant of the component's Transport class;
• Register the new factory service in the related FrameworkBundle config file (mailer_transports.php, notifier_transports.php or translation_providers.php) and add its class to the $classToServices list of the related method in FrameworkExtension;
• Add the #[\SensitiveParameter] attribute to the arguments that contain sensitive information (API keys, passwords, tokens, etc.);
• Use the current year in the copyright notice of the LICENSE file.

Update the Recipes

Add a Symfony Flex recipe for the new bridge to the symfony/recipes repository, so the needed environment variables (e.g. the DSN) are added to the .env file of the application when installing the bridge.

Update the Documentation

Each bridge is documented in its own README.md file, so explain there how to configure and use it. However, you must also update the following parts of the component documentation.

For a Mailer bridge:

• Add the new bridge to the list of third-party transports;
• Add its available DSN formats to the list of DSN formats of that same section;
• If the new bridge supports tags and metadata, add it to the list of transports that support them in the Mailer docs;
• If the new bridge supports webhooks, add it to the list of providers in the Webhook docs.

For a Notifier bridge:

• Add the new bridge to the list of the related Notifier channel (SMS, chat, push, etc.);
• If the new bridge supports webhooks, add it to the list of providers in the Webhook docs.

For a Translation bridge:

• Add the new bridge to the list of translation providers;
• Add its available DSN formats to the list of DSN formats of that same section.