wikimedia/mediawiki-extensions-AbuseFilter
1
0
Fork 0
mirror of https://gerrit.wikimedia.org/r/mediawiki/extensions/AbuseFilter.git synced 2024-11-15 02:03:53 +00:00
Code Issues Packages Projects Releases Wiki Activity
6724 commits 195 branches 0 tags 99 MiB
Commit graph

4 commits

Author SHA1 Message Date
libraryupgrader 5377ebe819 build: Updating dependencies 
composer:
* mediawiki/mediawiki-codesniffer: 36.0.0 → 37.0.0

npm:
* postcss: 7.0.35 → 7.0.36
  * https://npmjs.com/advisories/1693 (CVE-2021-23368)

Change-Id: I2b382f3bb236fb44eb24c6a257b13b8fd886541c
 2021-07-21 18:51:18 +00:00
Daimona Eaytoy b394956c22 Create a dedicated namespace for all consequences-related classes 
Change-Id: Ibc39593e34da36e57b640af0b5bbf2145f725e92
 2020-12-18 19:27:33 +00:00
Daimona Eaytoy d351d7150b Always take into account custom actions 
$wgAbuseFilterActions shouldn't be used normally, as it excludes actions
registered by other extensions.

Note: mw:Extension:AbuseFilter#Integration_with_other_extensions should
be updated after merging.

Bug: T239348
Change-Id: I89b3f0228eacdf145e8f2dd2a5602d0c7ce75a86
 2020-12-03 21:39:35 +00:00
Daimona Eaytoy 210cf29658 Add an interface for exporting/importing filters 
The main benefit of having a dedicated interface is that we can easily
change the output format. So we're now using a custom array without
references to the DB schema, thus making the import/export process
completely independent from the schema.

Change-Id: I4c0de41d914baf1e9a0e588bd31f95b3524a424b
 2020-11-18 22:06:09 +00:00