Kunal Mehta 9ecf62ead3 Update lint errors via the job queue ... The job queue will allow us to have better flood control and rate limiting instead of trying to do all the database writes as soon as parsoid contacts MediaWiki. On the downside, this means it may take longer for changes to be reflected in the database and to users, but we already have no promise for that, so it seems okay. Note that if you don't have a job queue runner set up, you'll need to run the runJobs.php script every time to have the jobs execute. Change-Id: I25fd54734aca4dab09711e7f6aee027654931300		2016-11-15 11:31:45 -08:00
..
ApiQueryLintErrors.php	Store linter_cat names in a separate table	2016-11-03 14:51:10 -07:00
ApiRecordLint.php	Update lint errors via the job queue	2016-11-15 11:31:45 -08:00
CategoryManager.php	Store linter_cat names in a separate table	2016-11-03 14:51:10 -07:00
Database.php	Store linter_cat names in a separate table	2016-11-03 14:51:10 -07:00
Hooks.php	Store linter_cat names in a separate table	2016-11-03 14:51:10 -07:00
LintError.php	Initial commit	2016-10-17 16:02:53 -07:00
LintErrorsPager.php	Store linter_cat names in a separate table	2016-11-03 14:51:10 -07:00
RecordLintJob.php	Update lint errors via the job queue	2016-11-15 11:31:45 -08:00
SpecialLintErrors.php	Store linter_cat names in a separate table	2016-11-03 14:51:10 -07:00