Investigate consuming Scriban as a submodule rather than nuget package
NeilMacMullen opened this issue · 1 comments
Scriban is highly optimised for fast generation of web pages. There are a few syntactic tweaks that would make it a little more pleasant to use in Textrude at the expense of losing a little performance/generality but which don't fit in well with the original codebase. (Not to put too fine a point on it, there are some "hacks" which would be acceptable for Textrude scenarios but not more broadly) e.g. scriban/scriban#322, scriban/scriban#324, scriban/scriban#319, multiline pipe-chains etc)
Implementing this would be a bit of a PITA and we'd want to track changes to the original codebase, ideally with the intention of returning to nuget consumption at some point. I'm not even sure how feasible it is - that needs to be evaluated.
Closing this. Although it would be nice to find a hack for terser lambda syntax, the other drivers for this are now implemented in the nuget package..