Vincent Prouillet
Vincent Prouillet
It is the intended behaviour, blocks are found when parsing the templates, `include` are not embedded in the AST, they are just their own nodes in it. That's unlikely to...
That's due to the way the errors are done in Tera, changing that would be a breaking change but it should be improved for the next major version.
Which line? Your link is pointing to a file.
I don't think so, the issue is that we are not displaying the source as well
It's the same yes. The current parser is not very smart and doesn't handle cases like this or macros well. It will be fixed for v2
Good idea but that's a breaking change, so for the next major version
This is following OWASP recommendations (https://cheatsheetseries.owasp.org/cheatsheets/Cross_Site_Scripting_Prevention_Cheat_Sheet.html#rule-1-html-encode-before-inserting-untrusted-data-into-html-element-content) and I don't think escaping it breaks anything
Thanks, I'll merge it for the next major version
It looks like you're using Tera::one_off from the template name, how are you using `render_str` then?
Can you past the whole Tera instantiation and the error you get?