Sébastien Ros

No it would have a `TextWriter` argument and the requested path to write some text directly to the result. It could also log stuff, or throw an exception, anything.

I assume the MVC View Engine could be extended with such tag. And probably also handle Tag Helpers (note Tag Helpers is already implemented in Orchard Core so that might...

I couldn't find the code where the `for` tag is used and shows how the current value is replaced by the page, like in this example https://github.com/Shopify/liquid/blob/eab13a07d9861a38d993d2749ae25f06ff76426b/performance/tests/vogue/blog.liquid

It's actually a feature that is provided by the "view" engine since it will also require extensibility for caching the files. Hence the template engine itself doesn't provide that out...

Note: - Add `IndexerAccessors` too. - Provide generic implementations - Member and Indexer are only used in `ObjectValue`.

> it might suffice to by default block access to non-public properties, disallow write (is that possible in Fluid?) and block GetType() / Reflection. Then options to allow That's the...

> project and item templates @hishamco I don't think this would be useful

Looks like a CMS feature ;) we have the same thing in Orchard. Are you using the FluidMvcViewEngine engine or just the FluidViewEngine ?

Do you expect the liquid files to be on disk? This is what it's doing if you don't set the custom file provider also in `FluidMvcViewOptions`.

Can you help me by creating a unit test that fails when using a "fake" file provider? There are existing ones with such a provider in the repos. I just...