You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/book/v6/core-features/rendering-and-sending-emails.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ To compose and send an email, a solid implementation of `TemplateRendererInterfa
8
8
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.
9
9
10
10
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.
12
12
13
13
With the new solution, `MailService` requires no implementation of any renderer because it no longer has to render templates internally.\
14
14
Instead, an implementation of `Api\App\Template\RendererInterface` is first injected in the handler:
0 commit comments