Daimona Eaytoy 2a0246ddb5 Remove ancient permission checks ... In both SpecialAbuseLog and ApiQueryAbuseLog, we use Title::getUserPermissionsErrors to check if the user is allowed to perform 'abusefilter-log' on the API page... However, this is a completely redundant check (which is also pretty expensive and queries the master): for the SpecialPage, we can specify the required right in the constructor and use checkPermissions, and for the API we can simply use checkUserRightsAny. If I'm not mistaken, there's no benefit in using getUserPermissionsErrors. Change-Id: I4c4dbace67b24cc1f45e50ab1c0d251522935513		2019-01-31 21:16:18 +00:00
..
ApiAbuseFilterCheckMatch.php	Allow users with abusefilter-view-private to use testing interface	2018-06-24 14:10:38 +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	Add phan configuration	2018-04-30 08:32:58 +00:00
ApiQueryAbuseFilters.php	Revert "Revert "Add typehinting for every object-only parameter""	2018-11-15 10:09:16 +01:00
ApiQueryAbuseLog.php	Remove ancient permission checks	2019-01-31 21:16:18 +00:00