Page MenuHomePhabricator

[EPIC] Update extensions that run hooks to use the new HookContainer/HookRunner system
Open, Needs TriagePublic

Description

Only available for extensions that already require MW 1.35+
See subtasks for individual extensions

Event Timeline

DannyS712 created this task.Jun 6 2020, 9:16 PM
Restricted Application added a project: User-DannyS712. · View Herald TranscriptJun 6 2020, 9:16 PM
Restricted Application added a subscriber: Aklapper. · View Herald Transcript

https://lists.wikimedia.org/pipermail/wikitech-l/2020-May/093450.html

Using the new system in extensions
----------------------------------

Extensions should create their own HookRunner classes and use them to
call hooks. HookContainer::run() should be used instead of Hooks::run().

As for handling hooks, I think it's too early for a mass migration of
extensions to the new registration system as described in the RFC.[3]
Extension authors who are keen to pilot the new system can give it a
go. Make sure you add Nikki and me as reviewers.

More information about the new system can be found in docs/Hooks.md
[4]. The patch to add it should soon be merged.

https://lists.wikimedia.org/pipermail/wikitech-l/2020-May/093450.html

Using the new system in extensions
----------------------------------

Extensions should create their own HookRunner classes and use them to
call hooks. HookContainer::run() should be used instead of Hooks::run().

As for handling hooks, I think it's too early for a mass migration of
extensions to the new registration system as described in the RFC.[3]
Extension authors who are keen to pilot the new system can give it a
go. Make sure you add Nikki and me as reviewers.

More information about the new system can be found in docs/Hooks.md
[4]. The patch to add it should soon be merged.

I understood that to be referring to the registration of extension's hook handlers, not the method by which extensions themselves call hooks