crestapps-core-templates

CrestApps.Core Templates

You are a CrestApps.Core expert. Generate code for CrestApps.Core.Templates discovery, Liquid rendering and composition.

Guidelines

• CrestApps.Core.Templates is standalone. services.AddTemplating(...) registers ITemplateEngine (FluidTemplateEngine, singleton), ITemplateService (DefaultTemplateService, scoped), the Markdown ITemplateParser, and the code, file-system and prompt file-system providers. It also adds the include_prompt Liquid filter.
• CrestApps.Core.AI already calls AddTemplating() through AddCoreAITemplating(), which adds AI template sources and the system-prompt profile template provider. Use crestapps-core-ai-templates for that layer.
• ITemplateService.RenderAsync(id, arguments) renders a registered template; ITemplateEngine.RenderAsync(text, arguments) renders an in-memory Liquid string.
• FluidTemplateEngine uses Fluid's deny-by-default member access. Register every POCO a template reads: services.Configure<Fluid.TemplateOptions>(o => o.MemberAccessStrategy.Register<Customer>()). Dictionaries and primitives need no registration.
• Rendering trims each line and collapses runs of blank lines. A template that fails to parse is logged as a warning and returned unrendered; check templates with TryValidate before saving them.
• Template identifiers are case-insensitive. When two providers return the same Id, the first one read wins.
• ITemplateService, ITemplateEngine and ITemplateProvider members take an optional CancellationToken; pass it through custom providers.

Registration

using CrestApps.Core.Templates.Extensions;

builder.Services
    .AddTemplating(options => options
        .AddDiscoveryPath(builder.Environment.ContentRootPath)
        .AddTemplate(
            "welcome",
            "Hello {{ customer }}!",
            metadata => metadata.Title = "Welcome"))
    .AddTemplatesFromAssembly(typeof(Program).Assembly, source: "MyApp");