More Callbacks/Hooks
BBot currently uses hooks for certain commands which greatly simplified module development and increased speed. Now, should BBot be converted to use more hooks to avoid passing unnecessary data to modules which don't need it? For example, the get_notice method and the get_raw method are not used in very many modules, so converting them to use callbacks/hooks would allow modules to request this data if needed.
Blueprint information
- Status:
- Not started
- Approver:
- BBot Core Developers
- Priority:
- Medium
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Discussion
- Series goal:
- None
- Implementation:
-
Not started
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
I believe that BBot should be converted to use more hooks, for the sole reason that it will then not be passing unnecessary data to modules.
Having said that, I believe we should consider specific things here. First, are we trying to make module development user-friendly? Second, if we are trying to make module development more user-friendly, would converting BBot into using more hooks mean more work for module developers? These two questions must be answered before we can decide what we're going to do about this.
--EvilPhoenix
-------
I think that using hooks is quite simple, but I wrote the code for them so I can't really say. The big problem is that it makes the API somewhat inconsistant. If some data is passed to the module's methods and other data is passed to a hook, it might over-complicate the api.
--AJ00200
-------
