As an output of the Parser, Parsoid lints should be added to the ParserOutput when useParsoid is set.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Stalled | None | T324931 Clean up open RESTBase related tickets | |||
| Open | None | T262315 <CORE TECHNOLOGY> API Migration & RESTBase Sunset | |||
| Resolved | Jgiannelos | T344944 Move Parsoid endpoints out of RESTBase | |||
| Resolved | daniel | T359964 Move page lint job outside of restbase request/response cycle to allow completely disabling cassandra writes | |||
| Restricted Task | |||||
| Resolved | daniel | T361013 Update lint tables independently of changeprop/restbase | |||
| Resolved | daniel | T361413 Parsoid should perhaps use LinkUpdate job for lints instead of special Linter API/Hook | |||
| Open | BUG REPORT | None | T341659 Please report linter-errors in parse-API too | ||
| Declined | None | T361411 Parsoid lints should be added to ParserOutput |
Event Timeline
Comment Actions
Note that I'm not 100% convinced we should do this -- see the caveats in T361413: Parsoid should perhaps use LinkUpdate job for lints instead of special Linter API/Hook.
Comment Actions
Our current thinking is that we want lints to be more asynchronous, not less, because of issues like the recent write overload from the empty-alt-text lint. This task would be part of making lints always-synchronous. Since (at the moment) we're not going that direction, I'm going to resolve this task as declined. We can always reopen if we switch directions.