Replies: 1 comment 3 replies
|
But this would make language linters and formatters scream because Jinja syntax breaks the language syntax. If you use VS Code, have you checked https://marketplace.visualstudio.com/items?itemName=samuelcolvin.jinjahtml? This enables syntax highlighting for both Jinja and the language. My experience has been very positive so far. WDYT? |
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
To automatically benefit from syntax highlighting in code editors, it seems more appropriate to use extended extensions such as
script.jinja.py,doc.jinja.txt,data.jinja.yaml, etc. rather thanscript.py.jinja,doc.txt.jinja,data.yaml.jinja, etc.I think it's more useful to have syntax highlighting for
Python,YAML, etc. than forJinja, which is used in small pieces that are easy to debug.Furthermore, this is easy to append
.jinjato file names when file extensions are hidden.Best regards.
PS: as someone who uses non-distributable
bashscripts, I really appreciate the update regarding templates offered bycopier.All reactions