We need a way to register custom extensions from localsettings.js. These should provide handlers that work on the token stream (by emitting tokens) or on the DOM (by converting the extension tag into an HTML DOM), and in the serializer (to convert an extension node back to wikitext).
The details are hashed out in https://www.mediawiki.org/wiki/Parsoid/Extension_registration_interface.
Version: unspecified
Severity: normal
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Add a generic extension registration mechanism | mediawiki/services/parsoid | master | +235 -227 |
Most extensions (both tag extensions and parser functions) operate independently and directly return the expected content. This enables parallel processing, caching and fairly straightforward preview of individual invocations in VE.
In the WMF projects the only exception to this rule is Cite, which needs to collect all citations in a page. I would caution against supporting general global content processing from extensions beyond Cite unless there is a really good reason to do so. In most cases I think it would be preferable to directly return the expected content from the parser function or tag extension.
Change 256171 had a related patch set uploaded (by Arlolra):
WIP: Add a generic extension registration mechanism
The mechanism exists ... but documenting the exposed API and determining the appropriate helpers will come as we iterate on a few use cases.