In this epic, we'll make changes to the REST endpoints that serve Parsoid HTML so that they use and save output to the cache.
At the end of this epic, it should be possible to use the Parsoid REST endpoints directly, without using RESTBase.
In this epic, we'll make changes to the REST endpoints that serve Parsoid HTML so that they use and save output to the cache.
At the end of this epic, it should be possible to use the Parsoid REST endpoints directly, without using RESTBase.
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Stalled | None | T324931 Clean up open RESTBase related tickets | |||
In Progress | None | T262315 <CORE TECHNOLOGY> API Migration & RESTBase Sunset | |||
Resolved | MSantos | T264669 Move VE API from RESTBase into core. | |||
Invalid | None | T262572 Use Parsoid-specific Parser Cache for Visual Editor | |||
Invalid | None | T262605 Parsoid REST API Client gets a speedy result | |||
Duplicate | None | T262593 MediaWiki Developer stores different HTML output for different language variants in the parser cache | |||
Duplicate | None | T262586 MediaWiki Developer stores parse metadata in parser cache | |||
Resolved | • eprodromou | T262604 Reader quickly reads a wiki page | |||
Resolved | • Pchelolo | T263587 CAPEX for ParserCache for Parsoid |