WIP: implement jinja templated includes #698
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a sort of "hey, wouldn't it just work if.." WIP PR. It allows specifying variables to
[include]statements, e.g.:and then
foo.cfgcan use jinja directives with{!% %!} {! !}(with the added!) to do templating and variable expansion that's resolved directly at include time, e.g.foo.cfg:The entire included file is treated as a template and rendered before being passed to the parser. Variables get maintained in an include chain -- if
foo.cfgincludes a file,FOOandTHINGwill be available there too.I still need to see how this interacts with SAVE_CONFIG (if at all). All this enables things like:
Checklist