Reimplement _unescape_entities routine.

</?text:s.*?> entities are not longer escaped.
This functionallity was used when secretary handled plain text
jinja instructions. This now is no longer supported since the
official method to add instructions is through input fields.
This commit is contained in:
Christopher 2015-12-21 11:29:41 -06:00
parent 5daa1a2c2b
commit 3a2b4b9c3b
2 changed files with 33 additions and 22 deletions

View file

@ -43,12 +43,6 @@ class RenderTestCase(TestCase):
'{{ a &lt; b }}' : '{{ a < b }}',
'{% a|filter &lt; b %}' : '{% a|filter < b %}',
'<node>{% a == b %}</node>{% else if a &lt; b %}': '<node>{% a == b %}</node>{% else if a < b %}',
# test scapig of multiple spaces, even encoded as <text:space> nodes
'{{ if <text:s> multiple_spaces }}' : '{{ if multiple_spaces }}',
'{{ if </text:s> multiple_spaces }}' : '{{ if multiple_spaces }}',
'{{ if <text:s/> multiple_spaces }}' : '{{ if multiple_spaces }}',
'{{ if <text:span/>[1,2,3]<text:span>&lt;</text:span>2 }}': '{{ if [1,2,3] < 2 }}',
}
for test, expect in test_samples.items():