Skip to content

Commit a0b49b1

Browse files
committed
Issue #104: how to send an email and parse the content
Signed-off-by: horea <[email protected]>
1 parent 96f916f commit a0b49b1

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ To compose and send an email, a solid implementation of `TemplateRendererInterfa
88
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.
99

1010
The solution is a custom [`Api\App\Template\Renderer`](https://github.com/dotkernel/api/blob/6.0/src/App/src/Template/Renderer.php) implementing [`Api\App\Template\RendererInterface`](https://github.com/dotkernel/api/blob/6.0/src/App/src/Template/RendererInterface.php).\
11-
This is a lightweight renderer, aimed at rendering a combination of **PHP** and **HTML** files with phtml extension.
11+
This is a lightweight renderer, aimed at rendering a combination of **PHP** and **HTML** files with `phtml` extension.
1212

1313
With the new solution, `MailService` requires no implementation of any renderer because it no longer has to render templates internally.\
1414
Instead, an implementation of `Api\App\Template\RendererInterface` is first injected in the handler:

0 commit comments

Comments
 (0)