You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ability to use multiple templates at the same time and depend on them (similar to Templer structures, but uses templates as structures you can depend on)
Ability to have logic that decides what files get rendered
Implementation:
variables and defaults are passed to all templates and all questions are collected from the dependency templates
issue Configurator for each template given global settings
keep ordered Configurator.dependencies list of templates
provide include/exclude options for files
pre/post hooks for executing dependencies
document local commands can be used as simple as just commands inside a project
I think that this risks making templates horrible to maintain. You would have problems like the main template not be able to change because other templates depended on it's variables, then if you did change variables, you would need version pins between templates.
I might not be thinking the above through thoroughly, but mrbob is nice principally because it's simple - IMO this goes the way of paster/zopeskel making it too complex to maintain beyond a few experts, for not much benefit. Am I wrong?
Goals:
Implementation:
Configurator.dependencies
list of templatesThe text was updated successfully, but these errors were encountered: