Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
[dev.icinga.com #9685] Deprecate Module::registerHook() in favor of Hook::provideHook() #1861
This issue has been migrated from Redmine: https://dev.icinga.com/issues/9685
Created by tgelf on 2015-07-21 09:15:57 +00:00
As we cannot pass config to hook constructors I guess there is no way of "hooking" the same class twice in a meaningful way. Hooking multiple classes from the same module for the very same hook might however occur. There is no reason why we should force people to invent an immaginary key in that case. We should IMO discuss whether further improvements (pass the key to the constructor, allow for a way to defer loading of a specific config in an anonymous function) would make sense. What would then once again allow for registering the same class multiple times, as with different configs it might absolutely make sense.
2015-11-12 17:33:51 +00:00 by tgelf 6d186aa
2015-11-13 11:45:41 +00:00 by tgelf 3306a41
2015-11-13 16:37:02 +00:00 by tgelf 54db2c9
2015-12-21 09:30:40 +00:00 by elippmann 8835552
2015-12-21 09:31:12 +00:00 by elippmann f2d54af
Updated by icinga-kanban on 2015-11-13 16:45:02 +00:00
Build !#1134 triggered by the commits 30f8faf, fd71653, cd16206, 2589fbc, b735210, 6394cec, 0e709d5, ff2c96e, 35d3342, f3cb1f9, 4b9607a, 8fa33ce, 380f11d, b718938, 997c5a0, b66e4df, 54db2c9, a24bf32, dc3c787, e6903b3, 52159c2, d903f85, 576747f failed.
Updated by elippmann on 2015-12-18 09:20:14 +00:00