Issue casued by Task.WhenAll when underlying tasks use types that are not threadsafe about servicecomposer.aspnetcore HOT 5 CLOSED

Thanks for looking into this @markphillips100. I never faced the issue myself but always suspected it was there.

Would it be interesting to have an extension point before each handler invocation? The extension point could expose the service provider and allow the creation of a child scope for each handler if needed.

from servicecomposer.aspnetcore.

Not sure that it's needed, or more specifically, something that this lib should provide and best left for developers to supply it themselves as required.

For example, I tend to have small handlers which pass a request type to a mediator. The implementation of those mediator commands can inject IServiceProvider if they require it. So in my case having the handler be supplied IServiceProvider would end up not being used as mediator wouldn't (cannot) use it directly.

I guess I just wanted to maybe surface it in documentation perhaps that developers should be aware of the thread safety being imposed is all. Just a note perhaps, what do you think?

from servicecomposer.aspnetcore.

Makes sense to at least provide some documentation. I'll craft it. Thanks.

from servicecomposer.aspnetcore.

Raised #371. @markphillips100 can you have a look?

from servicecomposer.aspnetcore.

Looks good @mauroservienti

from servicecomposer.aspnetcore.