Skip to content

Commit 3e8480a

Browse files
committed
Issue #104: how to send an email and parse the content
Signed-off-by: horea <horea@rospace.com>
1 parent 88628e1 commit 3e8480a

1 file changed

Lines changed: 0 additions & 1 deletion

File tree

docs/book/v6/core-features/rendering-and-sending-emails.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,6 @@
33
In the previous versions of Dotkernel API we have been composing email bodies using Twig from the mezzio/mezzio-twigrenderer package.\
44
In the current version of Dotkernel API, we introduced the core mail service Core/src/App/src/Service/MailService which is responsible for sending all emails.
55

6-
76
Being a core service, MailService is used across all projects implementing the Core architecture.\
87
To compose and send an email, a solid implementation of TemplateRendererInterface was required to be injected into MailService, because each method rendered and parsed their respective templates in place before sending an email.
98
This is acceptable with other Dotkernel applications which in most cases return a rendered template, but being that Dotkernel API mostly returns JSON objects, rendered with a different renderer, Twig had to be replaced with a lighter solution.

0 commit comments

Comments
 (0)