Spin off from #2001310: Disallow firing hooks during update. That issue is making the update system more robust and testable, but has some tricky code in it that could use more thorough review. To help focus that work, this issue just extracts the part of that one that moves most of the update_module_enable() implementation into a new class: UpdateModuleHandler.
This patch is almost a direct copy/paste of update_module_enable() to UpdateModuleHandler::enable(), except it makes UpdateModuleHandler::enable() conform to ModuleHandlerInterface::enable(), which means there's a little wrapping code retained in update_module_enable() to be cleaned up in the other issue.
Please credit chx on commit, since he wrote the initial patch from which this is extracted.
Comment | File | Size | Author |
---|---|---|---|
update_module_enable.patch | 10.73 KB | effulgentsia | |
Comments
Comment #1
effulgentsia CreditAttribution: effulgentsia commentedNote that either this patch, or #2004784-5: Move module install/uninstall implementations into ModuleInstaller will need a reroll after the other one lands. I can reroll either so have no preference as to which is committed first.
Comment #3
tim.plunkettupdate_module_enable.patch queued for re-testing.
Comment #4
Berdir#2001310: Disallow firing hooks during update is RTBC and will likely go in after the tests passed, can we close this again?
Comment #5
effulgentsia CreditAttribution: effulgentsia commentedNot sure what you mean by "again", but yes.