beezup / dotnet-codegen Goto Github PK

Not being able to dynamically register helpers is a serious drawback and we lose a lot of the initial flexibility handlebars provide as a template engine.

Maybe it would be a good idea to allow a range of assemblies as command line argument to add to the registration process assembly scanning?

Of course, dynamic assembly loading is always a tricky feature to secure: dependencies, .NET version etc... But it would at least leave a door open.

What do you think?

Currently, we need to provide one, and one only template folder when applying templates.
Could we update it to multiple folders?

Uses cases would be template folder logical division in a project, or a third party tool build on top of code-gen allowing template extensibility for its users (i.e ./third-party-app-templates and ./third-party-app user-templates)

What do you think?

I pertinent, I will of course do the PR.