Problem/Motivation

Currently an email could be handled by multiple EmailBuilder implementations: one specific to the type/sub-type and another more general one for all emails of the type. Normally this is not wanted - the specific email builder was presumably written to override the behaviour.

Proposed resolution

Only call the most specific EmailBuilder. It can always call/sub-class the more general one if wishes to inherit some behaviour.

Remaining tasks

User interface changes

API changes

Data model changes

CommentFileSizeAuthor
#2 symfony_mailer.one-builder.3349697-2.patch928 bytesadamps

Comments

AdamPS created an issue. See original summary.

adamps’s picture

adamps commented
Status: Active » Needs review
StatusFileSize
new symfony_mailer.one-builder.3349697-2.patch928 bytes

  • AdamPS committed c98e7968 on 1.x 
    Issue #3349697 by AdamPS: Only call one EmailBuilder
adamps’s picture

adamps commented
Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.