Generic Handler implementation only handles single generic argument and breaks existing implementations about mediatr HOT 5 OPEN

Is there a way to define a sensible limit internally, but then allow for this to be configurable?

from mediatr.

@jbogard any chance of a 12.2.1 to fix #989

If and when I get some time I can look at the above as I have implemented generic handlers in a few projects.

from mediatr.

Gah. Care to submit a PR?

from mediatr.

@jbogard I have a fix for the above issue.. My only question is what limitations should be present? What I mean is, should we let the user define handlers that have 10 type parameters, each with no constraint? You can see how this could be problematic for the user, right? My solution is to allow more than one generic type parameter but throw errors if the max number of generic type params is exceeded OR the max number of concrete class combinations is exceed OR if a timeout occurs. My question is.. what should those limitations be?

I'm also trying to figure out a way to test these scenarios since even defining a class that should throw an exception does so for all tests that call AddMediatR.

So, any discussion around this is welcome. I think I'm just going to create a PR and let discussion take place there.

from mediatr.

yes, I think there is a way to do this.. I will set up some configuration options with default values that can be overridden when calling AddMediatR.. I will have a PR coming today. We can probably discuss what is sensible in terms of default limitations in that thread.

from mediatr.