IssueTracker

I have top level jinja templates that import the same child jinja templates. In order for imports to work (with jinja templates) you MUST have a schema file- this is not the case with config files. If this requirement could be removed that would be good.

Otherwise I'd like a way to share a scheme file between multiple templates. I'm just using schema files for imports and nothing else so having to have a schema file for every top level jinja template with identical contents is a bummer.

How this might work:
You could have a param you can define at the top of your jinja templates (like imports) that explicitly points it to a schema file instead of relying on a specifically named schema file. Then multiple templates could point to the same schema