Is support aot?

[Cricle]

I try

class A
{
    public int D1 { get; set; }
    public int D2 { get; set; }

    public B B { get; set; }

    public IList<B> Bs { get; set; }
}
class B
{
    public string W1 { get; set; }
}

            var f = new FluidParser(new FluidParserOptions { AllowFunctions = true });
            var temp=f.Parse("""
                These shoes are awesome! {{ D1 }} {{ B.W1 }}
""");
            var a = new A { D1 = 123, B = new B { W1 = "456" } };
            Console.WriteLine(temp.Render(new TemplateContext(a)));

dotnet run

Result is These shoes are awesome! 123, but when I try dotnet publish -c Release -r win-x64 -p:PublishAot=true, result is These shoes are awesome!

[hishamco]

Which version?

[lahma]

Fluid currently isn't AOT compatible so as types are dynamically accessed the results will be wrong, like you've noticed.

[hishamco]

-p:PublishAot=true

Oops I didn't notice the flag, thanks @lahma, that's why I was asking myself why the title contains AOT :)

[Cricle]

Has any plan to support aot compile in the feature？
Or has any method to make it work？

[sebastienros]

Has any plan to support aot compile in the feature？

I started some work around it, but haven't made progress in a year.
Could you describe your scenario where you need AOT?

[Cricle]

I am currently trying to create a program that interacts with GitLab and other websites through webhook. I want to use Microsoft's' cloud native 'approach. Currently, all components used except for Fluid can be AOT enabled, so I am wondering if Fluid also supports AOT.

Thanks

[lahma]

Would probably require use of source generators and non-trivial amount of work.

[Cricle]

I would try to write object to FluidValue source generation use roslyn, but it will be defined like json serialization such as ignore, deep...

I think it will drop the reflection in model use.

[lahma]

Please draft a PR to demonstrate your ideas 👍🏻

[Cricle]

I will try to do it

[jinjaeyeon]

Any updates?

[sebastienros]

• IsDynamicCodeSupported should guard the code paths using reflection. e.g., https://github.com/sebastienros/parlot/blob/3194a70573be66228b54c124d142b11c1dbb3180/src/Parlot/Fluent/Parser.TryParse.cs#L39
• Source code generation could be used to evaluate model properties. Devs would have to describe/opt-in specific model classes in Fluid to evaluate model properties. Check existing solutions that provide model metadata (https://github.com/serdedotnet/serde?tab=readme-ov-file is a serializer, there must be existing libraries that only do reflection replacement in aot)