Some questions and suggestions

[Markz878]

Hi, I was trying out MediatR alternatives, and this this really seems to be the cleanest solution I found. I really like the convention based approach, and the easy source generation debugging. Unlike one other source generation library, this also doesn't require unnecessary DI registrations if some services are not actually used in some project.

I have a few questions/suggestions:

1. To ease the adaptation coming from MediatR, have you considered replacing Invoke with Send?
2. Any idea if it is possible to create a generic version of Invoke that could infer the the return type from the corresponding handler, so the return type doesn't have to be specified?
3. Could the MediatorDisableOpenTelemetry and similar properties be available in the AddMediator call options?
4. Any idea when the 1.0.0 version will be released?

[ejsmith]

Wow. Sorry, I never saw this post. Doesn't seem like github notifies for these?

1. I prefer Invoke over Send. To ease your transition, I'd recommend that you create an extension method for IMediator with a Send method that just forwards to Invoke.

2. Great idea and it was implemented already. :-)

3. I moved the code generation options to an assembly attribute so they are more discoverable and strongly typed. The code generator reads that attribute and uses it. I've thought about having the code generator attempt to read the AddMediator call / builder methods being set, but the problem with that is people will think they can do dynamic configuration and that won't work. I think the assembly attribute is a good compromise. I tried to make the defaults good so most people wouldn't need to change anything.

4. I think 1.0 will be coming very soon. Ideally, we would get more external validation from users like yourself. Can you take a look at things as they stand now and give feedback?

Thanks!