I just wrote some twig template which contained === and the parser failed:
Twig_Error_Syntax: Unexpected token "operator" of value "=" in "foo.html.twig" at line 19. in Twig_ExpressionParser->parsePrimaryExpression() (line 208 of vendor/twig/twig/lib/Twig/ExpressionParser.php).
I wonder whether twig should simply treat === as == or even provide some form of strict comparison.
dawehner
All 10 comments
=== does exist in Twig, but the name of the test is same as.
fabpot
on 11 Jan 2017
Right, I'm simply wondering whether === should be treated as "same as" automatically. I'm wondering whether its just me who is so stupid falling into that trap :)
dawehner
on 11 Jan 2017
This is really not like a feature request or so, I'm really just wondering
dawehner
on 11 Jan 2017
That's a good question and one for which we had a discussion in the past. The conclusion was that === is confusing for anyone not familiar with PHP. So, we decided to support it via same as instead.
fabpot
on 11 Jan 2017
One thing which could be done is to not support "===" but instead throw a helpful exception telling people about "same as"
dawehner
on 11 Jan 2017
That makes sense. Anyone willing to submit a PR for that? Could be done in the 1.x branch.
fabpot
on 3 Feb 2017
Absolutely
dawehner
on 4 Feb 2017
:+1: for closing PRs.
dawehner
on 2 Mar 2018
@dawehner It's not closed but merged ;)
fabpot
on 2 Mar 2018
Oh haha. Well even better :)
dawehner
on 2 Mar 2018
Related issues
xxfaxy
路
6Comments
rungta
路
3Comments
CriseX
路
4Comments
ericmorand
路
4Comments
reatang
路
4Comments
Most helpful comment
One thing which could be done is to not support "===" but instead throw a helpful exception telling people about "same as"