feat: refactor mailer client wiring and add validation wrapper #2130
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 change simplifies how MailClient instances are constructed and used:
NewMailClient
to encapsulate creation of the defaultMailmeMailer
ornoopMailClient
based on configuration.NewMailerWithClient
to allow injecting a customMailClient
.emailValidatorMailClient
, which wraps anotherMailClient
and ensuresValidate
is always called before sending. Removed inline validation logic fromMailmeMailer
.TemplateMailer
to consistently useMailClient
instead of the previousMailer
field.noopMailClient
with an optionalDelay
field to simulate latency in tests.EmailValidator
fromMailmeMailer
.Together, these changes make the mailer package easier to extend, improve separation of concerns, and provide hooks for testing latency and swapping in custom mail clients.