Open velios opened 9 months ago
I think this issue raises some good points.
Particularly about not being able to unregister hooks. That's a key feature missing for dev time!
These are indeed very good points! I'm not sure when I'll be able to bring my full attention to them, but I hope to soon
@flyingmachine Can you confirm or correct my assumptions? For example, I have a system.
I couldn't come up with a good example. But did I understand correctly that when I have a production system, I initialize hooks in component start section? And when I have a test system, I simply do not initialize the hooks and all side effects associated with this component stop working. Or is it better to initialize hooks in a separate virtual component? I can’t wrap my head around the whole idea, maybe you’ve thought about this and can share?
I also came up with the idea that since we do not indicate in which storage the hooks are contained, then we cannot clear them in the component's stopping loop. This means that if we abandoned some hook during replay development and rebooted the system, then we do not have the opportunity to clean up the hooks associated with this component in order to reinitialize them again? Usually side effects in systems are associated with some component, is it worth managing them separately for each component or how to bypass this issue?