Changes between Version 3 and Version 4 of TracDev/JinjaChecker

Timestamp:

Jul 27, 2016, 9:47:08 AM (8 years ago)

Author:

figaro

Comment:

Cosmetic changes

TracDev/JinjaChecker

@@ -1 @@
-= `jinjachecker`
+= Jinjachecker
 
-Jinja2 is very helpful when it detects any kind of error, as you always end up with a meaningful backtrace. Nevertheless, it can be tedious to get the nesting of control structures right.
-
-To help with that problem, we wrote the [source:cboos.git/contrib/jinjachecker.py contrib/jinjachecker.py] tool.
+Jinja2 is very helpful when it detects any kind of error, as you always end up with a meaningful backtrace. Nevertheless, it can be tedious to get the nesting of control structures right. To help with that problem, we wrote the [source:cboos.git/contrib/jinjachecker.py contrib/jinjachecker.py] tool.
 
 It first analyzes the Jinja2 control structures, and tries to provide some helpful diagnostics in case of nesting or stylistic errors.
-It also adds curly braces to the statements, so if you have an editor which can do matching of brace pairs, you can quickly spot the origin o a nesting problem.
+It also adds curly braces to the statements, so if you have an editor which can do matching of brace pairs, you can quickly spot the origin of a nesting problem.
 
 Finally, while the indentation of the statements is free in Jinja2 templates, being consistent with it also helps to ensure a proper nesting.
@@ -13 +11 @@
 
 The command:
-{{{
+{{{#!sh
 python contrib/jinjachecker.py trac/wiki/templates/jwiki_view.html
 }}}
@@ -158 +156 @@
 
 == Known Issues
+
 The tool won't yet detect nesting mistakes when the Jinja2 control structure nesting and the HTML element nesting are both independently correct (e.g. errors like the one fixed in [68094c2ea/cboos.git]). //This might be fixed in a 3rd pass, doing XML validation after having replaced the Jinja2 start/end keywords with "equivalent" XML elements.//