"As a MediaWiki Developer, I want to set, get and purge HTML for a revision in the parser cache, so that I can quickly get the HTML for a revision."
Parsoid API has paths that take a revision ID as a parameter, so we should have a way to get the HTML for a revision.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Stalled | None | T324931 Clean up open RESTBase related tickets | |||
| In Progress | None | T262315 <CORE TECHNOLOGY> API Migration & RESTBase Sunset | |||
| Open | None | T264669 Move VE API from RESTBase into core. | |||
| Resolved | daniel | T267981 Implement /revision/{id}/html endpoint in core | |||
| Resolved | • WDoranWMF | T262597 MediaWiki Developer stores revision HTML in parser cache |
The description of the task and the title of the task don't seem aligned. Can you update or clarify?
Ok, I'm going to reroot this task to T267981 where we will be implementing parsoid-html handler for old revisions.
We have spent a lot of time evaluating current ParserCache and ultimately made a decision not to use it for old revisions, and use ObjectCache::localClusterInstance instead.
The interface and semantics of expiration policy is so different between latest and old revisions that it makes no sense to reuse existing ParserCache. Perhaps we can implement OldRevisionParserCache to incapsulate the code that will be shared between RevisionHTMLHandler and PoolWorkArticleViewOld. We shall see as we progress.