[go: up one dir, main page]

Page MenuHomePhabricator

[EPIC] Ensure all extensions on the Wikimedia cluster that use Parser hooks or implement tag hooks are retargeted for Parsoid
Open, MediumPublic

Description

Parsoid has a different API for extensions compared to the core parser. So, for Parsoid to replace the core parser for read views on the Wikimedia cluster, we need to update a subset of those extensions to retarget Parsoid.

Any extension that

  • is deployed on the Wikimedia cluster
  • uses a "parser hook" and/or
  • implements tag hooks

is impacted by this change.

Extensions that only use the "parser API" (which might mean: the extension just used whatever public method in Parser.php it happened to get its hands on) can optionally migrate over but is not necessary for transitioning to Parsoid Read Views. We'll continue to use the "core parser" for such extensions in the interim.

Cite, Poem, ImageMap, Gallery, Nowiki, Pre extensions have already been retargeted. We need to track down everything else and ensure they are updated.

This is a tracker task to ensure we track all extensions that need an update to ensure they are updated. Subtasks will be created for some specific extensions. Since there are going to be a lot of extensions that need tweaking and some tweaks might be minor, I may instead track these in a spreadsheet and create specific tasks on demand as needed.

Related Objects

StatusSubtypeAssignedTask
OpenReleaseNone
OpenNone
OpenNone
OpenNone
OpenFeatureNone
OpenNone
OpenNone
ResolvedArlolra
Resolvedssastry
Resolvedcscott
Resolvedcscott
Resolvedcscott
Resolvedcscott
ResolvedPRODUCTION ERRORLucas_Werkmeister_WMDE
ResolvedPRODUCTION ERRORabi_
ResolvedPRODUCTION ERRORcscott
ResolvedPRODUCTION ERRORroman-stolar
ResolvedNone
ResolvedNone
Resolvedmatmarex
Resolvedmatmarex
Resolvedssastry
Resolvedssastry
Resolvedssastry
Resolvedihurbain
ResolvedNikerabbit
ResolvedNikerabbit
Resolvedihurbain
Resolvedihurbain
Resolvedihurbain
Resolvedihurbain
Resolvedihurbain
ResolvedBUG REPORTihurbain
Resolvedssastry
Resolvedihurbain
ResolvedBUG REPORTihurbain
DeclinedBUG REPORTihurbain
ResolvedBUG REPORTihurbain
OpenBUG REPORTNone
ResolvedBUG REPORTihurbain
ResolvedBUG REPORTArlolra
Resolvedihurbain
ResolvedBUG REPORTihurbain
ResolvedFeatureihurbain
ResolvedBUG REPORTmatmarex
OpenBUG REPORTNone
OpenNone
Resolvedihurbain
Resolvedihurbain
Resolvedihurbain
Openihurbain
OpenNone
OpenNone
OpenNone
Resolvedcscott
OpenNone
OpenNone
Resolvedihurbain
OpenNone
OpenNone
OpenNone
OpenNone
DeclinedNone
DeclinedNone
OpenNone
Resolvedssastry
Resolvedssastry
OpenNone
ResolvedTheDJ
OpenNone
OpenNone
OpenNone
OpenNone
OpenNone
DuplicateNone
OpenNone
OpenBUG REPORTNone
OpenBUG REPORTNone
OpenNone
OpenBUG REPORTNone
OpenNone
OpenNone

Event Timeline

ssastry triaged this task as Medium priority.Jul 24 2020, 9:12 PM
ssastry updated the task description. (Show Details)
ssastry renamed this task from [EPIC] Ensure all Parser API/Hook using extensions on the Wikimedia cluster are retargeted for Parsoid to [EPIC] Ensure all extensions on the Wikimedia cluster that use Parser hooks or implement tag hooks are retargeted for Parsoid.Dec 21 2020, 6:55 PM
ssastry updated the task description. (Show Details)

Ooops. I am going to add back all those subtasks (except 3D which isn't a tag extension or uses parser hooks afaict). This epic isn't about read views necessarily - but about ensuring these extensions have native Parsoid handlers.

Are there some guidelines to ensure an extension is compatible with Parsoid? Is Manual:Tag extensions up-to-date?