Daimona Eaytoy 382751a707 Move conditions-related stuff inside AbuseFilterParser ... Instead of relying on static methods and members in the AbuseFilter class, move everything related to conditions inside the Parser, as the amount of used conditions is something pertaining a single AbuseFilter(Caching)Parser instance. This change requires changing some signatures and adding parameters, but will make introducing the new AbuseFilterRunner class easier (and that will clean signatures, too). Depends-On: I5b29ff556eca45fe59d15e2e3df4d06f1f6b3934 Change-Id: I7c1ea17adf7f42cf9260d416906bfbf3b8a20688		2019-06-19 15:14:17 +00:00
..
ApiAbuseFilterCheckMatch.php	Move conditions-related stuff inside AbuseFilterParser	2019-06-19 15:14:17 +00:00
ApiAbuseFilterCheckSyntax.php	Allow users with abusefilter-view-private to use testing interface	2018-06-24 14:10:38 +00:00
ApiAbuseFilterEvalExpression.php	Fix coding conventions exclusion rules	2018-04-20 08:40:18 +00:00
ApiAbuseFilterUnblockAutopromote.php	Replace deprecated cache-related functions	2019-02-09 16:01:57 +00:00
ApiQueryAbuseFilters.php	Revert "Revert "Add typehinting for every object-only parameter""	2018-11-15 10:09:16 +01:00
ApiQueryAbuseLog.php	Rewrite AbuseFilter::decodeGlobalName	2019-06-12 23:56:25 +00:00