Closed deathaxe closed 5 months ago
Perhaps the supported syntaxes in the readme should also be updated.
Maybe part of the next - somewhat larger step of refactoring HTML as it will automatically cause this package to support CSS/JavaScript/JSON/HTML/YAML automatically - with drastically reduced compiled syntax cache sizes.
Any chance of adding support for Jinja statements or comments? From the Jinja docs:
There are a few kinds of delimiters. The default Jinja delimiters are configured as follows:
{% ... %} for [Statements](https://jinja.palletsprojects.com/en/latest/templates/#list-of-control-structures)
{{ ... }} for [Expressions](https://jinja.palletsprojects.com/en/latest/templates/#expressions) to print to the template output
{# ... #} for [Comments](https://jinja.palletsprojects.com/en/latest/templates/#comments) not included in the template output
They already are.
Closing in favor of https://github.com/Sublime-Instincts/BetterJinja/pull/22
This PR suggests to add a YAML (Jinja) syntax, which extends ST's core YAML to embed jinja statements and expressions.
It does by intent not use
with_prototype
to be able to extend specific YAML contexts in proper ways to maintain meta scoping.Notes: