Fix how events are called and propagated
We know use `consume_event_#{event_name}` as the consume method pattern. Some places were calling methods based on early version of our APIs. Added extra coverage on missing parts of the framework.
Showing
Please register or sign in to comment