Thanks for bringing this to my attention. Null should definitely been possible to send (and compare with CheckEventValue).
Here are the final changes I’ve just made:
CheckEvent.cs
I’ve used reflection here so that assignable types work as well. It can be a bit slower, but also more flexible and convenient.
CheckEventValue.cs
I don’t know what I was thinking in my previous code. It doesn’t make a lot of sense the way I did it before 🙂
I think I was trying to only catch events of the exact specified T type, but was not really convenient. This now handles assignable types as well as nulls of course.