Transmitly.TemplateEngine.Fluid 0.3.0

Transmitly.TemplateEngine.Fluid

Transmitly.TemplateEngine.Fluid adds Fluid templating support to the core Transmitly library.

This package is typically used alongside:

• Transmitly
• a Transmitly channel provider such as Transmitly.ChannelProvider.Smtp, Transmitly.ChannelProvider.SendGrid, or Transmitly.ChannelProvider.Infobip

Install

dotnet add package Transmitly
dotnet add package Transmitly.TemplateEngine.Fluid
dotnet add package Transmitly.ChannelProvider.Smtp

Quick Start

using Transmitly;
using Transmitly.ChannelProvider.Smtp.Configuration;

ICommunicationsClient client = new CommunicationsClientBuilder()
	.AddSmtpSupport(options =>
	{
		options.Host = "smtp.example.com";
		options.Port = 587;
		options.UserName = "smtp-user";
		options.Password = "smtp-password";
	})
	.AddFluidTemplateEngine()
	.AddPipeline("order-shipped", pipeline =>
	{
		pipeline.AddEmail("orders@my.app".AsIdentityAddress("Orders"), email =>
		{
			email.Subject.AddStringTemplate("Order {{orderNumber}} has shipped");
			email.HtmlBody.AddStringTemplate(
				"""
				<p>Hello {{firstName}},</p>
				{% if trackingUrl %}
				<p>Your order has shipped. <a href="{{trackingUrl}}">Track package {{trackingNumber}}</a>.</p>
				{% else %}
				<p>Your order has shipped.</p>
				{% endif %}
				"""
			);
			email.TextBody.AddStringTemplate("Hello {{firstName}}, your order {{orderNumber}} has shipped.");
		});
	})
	.BuildClient();

var result = await client.DispatchAsync(
	"order-shipped",
	"customer@example.com".AsIdentityAddress("Ava Example"),
	new
	{
		firstName = "Ava",
		orderNumber = "A10023",
		trackingNumber = "1Z999",
		trackingUrl = "https://carrier.example/track/1Z999"
	});

Registration

Use either registration style:

new CommunicationsClientBuilder()
	.AddFluidTemplateEngine();

new CommunicationsClientBuilder()
	.TemplateEngine.AddFluidTemplateEngine();

To customize parsing, use the overload that accepts FluidParserOptions.

Template Sources

The engine works with the normal Transmitly template registration APIs:

• AddStringTemplate(...)
• AddEmbeddedResourceTemplate(...)
• AddTemplateResolver(...)

Behavior Notes

• Templates render against context.ContentModel.Model.
• Invalid Fluid templates currently return null rather than throwing from this package.
• A null content model is allowed; missing values render as empty output.
• The current Transmitly core supports only one template engine registration per CommunicationsClientBuilder.

Related Packages

• Transmitly
• Transmitly.TemplateEngine.Scriban

Copyright (c) Code Impressions, LLC. This open-source project is sponsored and maintained by Code Impressions and is licensed under the Apache License, Version 2.0.