[Mailer][WIP] Add Provider Templated Email functionality to Mailer #62664
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This allows developers to use the provider template system using the mailer component. Often using the provider template system is not a technical decision but made by marketing to allow them to control the content of the emails instead of waiting for developer time for changes to be made.
I've not added tests, changelog, exception messages, hardening, docs, etc incase it's not accepted. The concept is to add a
ProviderTemplatedTransportInterfacewhich allows the bridge to say if it supports the feature. There is a logical check in the in MessageHandler to say if the bridge supports it, I think the bridge should not need to be aware of functionalities if it doesn't support them so this keeps it out of that context.