mirror of
https://gerrit.wikimedia.org/r/mediawiki/extensions/AbuseFilter.git
synced 2024-09-24 02:38:16 +00:00
Merge "Distinguish AbuseFilter warnings and errors in VE"
This commit is contained in:
commit
671b8b7fb3
|
@ -11,11 +11,11 @@ mw.libs.ve.targetLoader.addPlugin( function () {
|
|||
};
|
||||
|
||||
ve.init.mw.AbuseFilterSaveErrorHandler.static.process = function ( data, target ) {
|
||||
var
|
||||
$message = $( $.parseHTML( ve.getProp( data, 'visualeditoredit', 'edit', 'warning' ) ) ),
|
||||
isWarning = ve.getProp( data, 'visualeditoredit', 'edit', 'code' ) !== 'abusefilter-disallowed';
|
||||
// Handle warnings/errors from Extension:AbuseFilter
|
||||
target.showSaveError( $( $.parseHTML( ve.getProp( data, 'visualeditoredit', 'edit', 'warning' ) ) ) );
|
||||
// Don't disable the save button. If the action is not disallowed the user may save the
|
||||
// edit by pressing Save again. The AbuseFilter API currently has no way to distinguish
|
||||
// between filter triggers that are and aren't disallowing the action.
|
||||
target.showSaveError( $message, isWarning, isWarning );
|
||||
// Emit event for tracking. TODO: This is a bad design
|
||||
target.emit( 'saveErrorAbuseFilter' );
|
||||
};
|
||||
|
|
Loading…
Reference in a new issue