[GH-ISSUE #174] Support for conditional and loop templating in render function #60

New issue

Closed

opened 2026-03-01 14:39:48 +03:00 by kerem · 4 comments

kerem commented

2026-03-01 14:39:48 +03:00

Owner

Originally created by @Ayo-Awe on GitHub (Apr 4, 2025).
Original GitHub issue: https://github.com/arikchakma/maily.to/issues/174

Hey @arikchakma, great work on the library!

I have a quick question.
I noticed that when using the render function, variables are replaced with placeholders like {{variableName}}, which is really useful for interoperability with external templating engines. However, I noticed that the same doesn’t apply to conditionals and loops.

It would be really useful if those could also be replaced with their templating equivalents—such as Handlebars' #if and #each.

For example:

{{#if author}}
  <h1>{{firstName}} {{lastName}}</h1>
{{/if}}

{{#each people}}
  <li>{{this}}</li>
{{/each}}

Would love to hear your thoughts!

Originally created by @Ayo-Awe on GitHub (Apr 4, 2025). Original GitHub issue: https://github.com/arikchakma/maily.to/issues/174 Hey @arikchakma, great work on the library! I have a quick question. I noticed that when using the `render` function, variables are replaced with placeholders like `{{variableName}}`, which is really useful for interoperability with external templating engines. However, I noticed that the same doesn’t apply to conditionals and loops. It would be really useful if those could also be replaced with their templating equivalents—such as Handlebars' [#if](https://handlebarsjs.com/guide/builtin-helpers.html#if) and [#each](https://handlebarsjs.com/guide/builtin-helpers.html#each). For example: ```handlebars {{#if author}} <h1>{{firstName}} {{lastName}}</h1> {{/if}} {{#each people}} <li>{{this}}</li> {{/each}} ``` Would love to hear your thoughts!

kerem closed this issue

2026-03-01 14:39:48 +03:00

kerem commented

2026-03-01 14:39:49 +03:00

Author

Owner

@arikchakma commented on GitHub (Apr 4, 2025):

Currently, we don't support that because we handle the replacement of the loop and the conditional. Kinda we are using that as a replacement of a templating engine. But it should be easy to add.

@arikchakma commented on GitHub (Apr 4, 2025): Currently, we don't support that because we handle the replacement of the `loop` and the `conditional`. Kinda we are using that as a replacement of a templating engine. But it should be easy to add.

kerem commented

2026-03-01 14:39:49 +03:00

Author

Owner

@Ayo-Awe commented on GitHub (Apr 4, 2025):

Oh, okay. That makes sense.

Unfortunately, my use case requires exporting the templates for use in a non-Node runtime.
But I'll give it a shot on my end, and let you know how it goes

@Ayo-Awe commented on GitHub (Apr 4, 2025): Oh, okay. That makes sense. Unfortunately, my use case requires exporting the templates for use in a non-Node runtime. But I'll give it a shot on my end, and let you know how it goes

kerem commented

2026-03-01 14:39:49 +03:00

Author

Owner

@arikchakma commented on GitHub (Apr 5, 2025):

Did you find any solutions for this one? It should be simple, imo.

@arikchakma commented on GitHub (Apr 5, 2025): Did you find any solutions for this one? It should be simple, imo.

kerem commented

2026-03-01 14:39:49 +03:00

Author

Owner

@Ayo-Awe commented on GitHub (Apr 5, 2025):

I still taking a look, but the approach I'm considering is customizing the rendered html of the repeat node.
I wouldn't mind some guidance if you have an idea of a way to go about it

@Ayo-Awe commented on GitHub (Apr 5, 2025): I still taking a look, but the approach I'm considering is customizing the rendered html of the repeat node. I wouldn't mind some guidance if you have an idea of a way to go about it

kerem referenced this issue

2026-03-01 14:40:10 +03:00

[PR #60] [MERGED] feat: section improvements & image size #121

kerem referenced this issue

2026-03-15 02:09:56 +03:00

[PR #60] [MERGED] feat: section improvements & image size #348