Bartosz Dziewoński 3b32cf00e9 Improve how the number of conditions is counted ... With the new behavior, the number of conditions in incremented when: * Evaluating a function * Evaluating a comparison operator (== === != !== < > <= >= =) * Evaluating a keyword (in like matches contains rlike irlike regex) Previously, the number of conditions was incremented when: * Evaluating a function * Entering the comparison operator evaluation mode This resulted in a number of surprising behaviors. In particular: * '(((a == b)))' counted as 4 conditions, not 1 * 'contains_any(a, b, c)' counted as 5 conditions, not 1 * 'a == b == c' counted as 1 condition, not 2 * 'a in b + c in d + e in f' counted as 1 condition, not 3 * 'true' counted as 1 condition, not 0 It is still possible to easily cheat the count by rewriting comparisons as arithmetic operations. I believe this is meant to advise users of the complexity of their rules and not really enforce strict limits. Bug: T132190 Change-Id: I897769db4c2ceac802e3ae5d6fa8e9c9926ef246		2016-04-09 16:16:27 +02:00
..
parserTests	Fix double escaping in AFPData::keywordLike()	2014-07-11 14:56:42 -07:00
phpunit	Improve how the number of conditions is counted	2016-04-09 16:16:27 +02:00
legacyParserTest.php	Allow running the AbuseFilter parser tests via phpunit	2013-07-08 19:22:43 +02:00