At the moment, things fail "silently" (either that or we get AVs based on "nil" references being returned where an object is expected).
Obviously this isn't acceptable in production code, so I need to implement complete error handling throughout the Event Engine. This should ideally be configurable in result by the implementing developer, and in the very least should populate an error log so the implementing developer knows that things aren't working as expected for whatever reason.
A lot of the internal "failure conditions" in the Event Engine actually stem from the Streamables Engine... so that work should be considered integral to this issue.
At the moment, things fail "silently" (either that or we get AVs based on "nil" references being returned where an object is expected).
Obviously this isn't acceptable in production code, so I need to implement complete error handling throughout the Event Engine. This should ideally be configurable in result by the implementing developer, and in the very least should populate an error log so the implementing developer knows that things aren't working as expected for whatever reason.