MediatR - Polymorphic Notification about dryioc HOT 11 CLOSED

I was able to resolve this by moving the INotification marker interface to a base class.

thanks for your help!

from dryioc.

Hi,
Could you create a complete test in DryIoc.IssueTests project?

from dryioc.

OK but do you agree this is a bug? Sorry not trying to be rude I just need to figure out if I need to swap DI containers if it is until a fix is made.

from dryioc.

I don't understand this fully. If I see, play with complete sample / test, it will speedup things.
I doubt that the problem is in DryIoc, cause we talk about basic feature. But again, hard to be sure until I see a full example.

from dryioc.

Ohh, what version of DryIoc do you use?

Now I have remembered that "maybe" related issue was fixed in v3.1 (now in preview). Try it out if you are using a lesser version.

from dryioc.

Ohh, what version of DryIoc do you use?

Now I have remembered that "maybe" related issue was fixed in v3.1 (now in preview). Try it out if you are using a lesser version.

The preview version did not resolve the issue.

from dryioc.

i had to go out of town unexpected for the weekend. is this something you would have time to investigate? it's literally as simple as the code sample i show.

any help would be great!

from dryioc.

Hopefully, will have time to check.

from dryioc.

Hi @mpaul31,

I have added the tests to demonstrate that it cannot be "simply" achievable. So it is not a DryIoc fault, nor the MediatR's. I tried the case without containers and MediatR with the same results.

First, you need to figure out how you would do it by hand, then we think how to automate it with libs.

from dryioc.

from dryioc.

In order to support such a notification we should construct something like this:

Func<N, Task> Handler =
    async n => await Task.WhenAll(new[] {  
        ((INHandler<N>)new NHandler()).Handle(n),
        ((INHandler<K>)new NHandler()).Handle(n)
    });

class K {}
class N : K {}
class NHandler : IHandler<N>, IHandler<K> {}

from dryioc.