Code Coverage |
||||||||||
Lines |
Functions and Methods |
Classes and Traits |
||||||||
| Total | n/a |
0 / 0 |
n/a |
0 / 0 |
CRAP | n/a |
0 / 0 |
|||
| 1 | <?php |
| 2 | |
| 3 | namespace MediaWiki\Extension\AbuseFilter\Hooks; |
| 4 | |
| 5 | interface AbuseFilterCustomProtectedVariablesHook { |
| 6 | /** |
| 7 | * Allows other extensions to define variables as protected variables. This has the effect of |
| 8 | * adding the variable to the $wgAbuseFilterProtectedVariables configuration value. A protected |
| 9 | * variable can only be used in a protected filter, which is not publicly accessible. |
| 10 | * |
| 11 | * Using this hook has the advantage of enforcing that the variable is always protected, even if |
| 12 | * it is removed from $wgAbuseFilterProtectedVariables. |
| 13 | * |
| 14 | * The values of protected variables are purged after $wgAbuseFilterLogProtectedVariablesMaxAge seconds. |
| 15 | * If the config is set to 0, then the protected variables are never purged. |
| 16 | * |
| 17 | * @since 1.44 |
| 18 | * @param string[] &$variables The variables which should be protected variables. |
| 19 | */ |
| 20 | public function onAbuseFilterCustomProtectedVariables( array &$variables ); |
| 21 | } |