Avinash Sonawane

Has this issue been fixed by #309? If yes then maybe we should close this issue.

Does v2 parser handle this too? continuing the above example: ``` {{ char_array in array }} // currently, this works {{ ["a", 'b', `c`] in array }} // currently, this...

Also, from tera documentation for [`in` operator](https://tera.netlify.app/docs/#in-checking): > While in the left hand side only literals/variables resulting in a number, a string and a boolean are supported. But as demonstrated...

Hi! Since this is related to parser I'm not opening a fresh issue. Does v2 parser handle this: ``` {% set char_array = ["a", 'b', `c`] %} {{ char_array !=...

First line is indeed false. But unfortunately, Tera throws parsing error on the next line. I hope v2 parser fixes that. :)

Adding more tests to check with parser v2. Parentheses with filter: ``` {{ 1 + ("foo" | length) }} // currently, doesn't work {{ (" foo " | trim) ~...

> The keywords `and` and `or` are also not allowed in brackets. 1. neither are the comparison operators (https://tera.netlify.app/docs/#comparisons) ``` {% if (a > b) and (a > c) %}...

Does it also handle these two: ``` {{ not (not a) }} {{ not not a }} ```

Great! Looks like we got the parser we needed :) Nice work!

Not any particular usecase at the moment. I was just thinking if comparison ops on strings make sense. :)