To facilitate refactoring of ParserOutput, it would be helpful to remove ::addOutputHook(). See T287216#7392138 for more discussion.
Description
Details
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Open | None | T305161 Hard-deprecate and remove @deprecated methods from ParserOutput | |||
Resolved | cscott | T292321 Remove ParserOutput::addOutputHook() |
Event Timeline
There's only 2 usages of this feature in extensions, none of them are deployed.
In LanguageSelector extension this is used to instruct a JS module to be added to OutputPage if a languageselector tag is used on a page. We can just add the module directly in the tag hook without all this mess.
Can also be done in the OutputPageParserOutput hook, which I think is going to be the preferred place to put this sort of finalization.
Change 760994 had a related patch set uploaded (by C. Scott Ananian; author: C. Scott Ananian):
[mediawiki/core@master] Deprecate the ParesrOutputHook functionality
Change 760994 merged by jenkins-bot:
[mediawiki/core@master] Deprecate the ParserOutputHook functionality
Change 776011 had a related patch set uploaded (by C. Scott Ananian; author: C. Scott Ananian):
[mediawiki/core@master] Emit deprecation warnings for ParserOutput::addOutputHook()
Change 776011 merged by jenkins-bot:
[mediawiki/core@master] Emit deprecation warnings for ParserOutput::addOutputHook()
Change 942499 had a related patch set uploaded (by C. Scott Ananian; author: C. Scott Ananian):
[mediawiki/core@master] Remove ParserOutput::addOutputHook() and related code
Change 942499 merged by jenkins-bot:
[mediawiki/core@master] Remove ParserOutput::addOutputHook() and related code