Page MenuHomePhabricator

Migrate Client hooks to extension JSON
Closed, ResolvedPublic

Description

To be broken down Later™. If this hasn’t been broken down by the time we want to pick it up, create subtasks then.

For hooks in the general ClientHooks class, just move the definition; however, for hooks that already have a dedicated handling class (such as EchoSetupHookHandlers), consider migrating to the new hook container system (T240307).

Five hooks are not registered in unit tests. We are inclined not to repeat this pattern, but to fix the tests so they work with those hooks, and then register the hooks unconditionally (T256253).

Related Objects

View Standalone Graph
This task is connected to more than 200 other tasks. Only direct parents and subtasks are shown here. Use View Standalone Graph to show more of the graph.
StatusSubtypeAssignedTask
ResolvedLadsgroup
ResolvedNone
ResolvedLadsgroup
ResolvedLucas_Werkmeister_WMDE
ResolvedTarrow
ResolvedLucas_Werkmeister_WMDE
ResolvedLucas_Werkmeister_WMDE
ResolvedLucas_Werkmeister_WMDE
ResolvedLucas_Werkmeister_WMDE
ResolvedLucas_Werkmeister_WMDE
ResolvedLadsgroup
ResolvedLadsgroup
ResolvedLadsgroup
ResolvedLadsgroup
ResolvedLadsgroup
ResolvedLadsgroup
ResolvedLadsgroup
ResolvedLucas_Werkmeister_WMDE

Event Timeline

Possibly depends upon T256253