The FileImporter currently does block the whole import if one of the revisions triggers a AbuseFilter warning. Instead we want to catch these ( potentially multiple ) warnings and show them to the user. Afterwards the user should be able to continue the import.
After the user submitted the form to start the import
- Detect and collect AbuseFilter warnings when validating the revisions
- Get back to the preview form and show ( probably at the top )
- One general warning explaining that some revision(s) the import triggered AbuseFilter
- The specific warning text(s) of the rules we triggered
- If the user hits submit again the import will continue and should not be blocked by the AbuseFilter
If the AbuseFilter triggers a block due to a rule ( even if it affects an old revision ) block the whole import and show the warning box for that rule. ( This should be the status quo in that regard )