Eric J. Smith

Absolutely! Totally appreciate the feedback. 🙂

As far as the tuple returns, you don’t have to use them if you don’t want to. The point is making it so that there isn’t any messaging framework in your handlers which makes testing a lot nicer. No message context or even IMediator to publish notifications is required in your handlers.

Thanks for the feedback! We could have an IHandler marker interface that we look for instead of by naming convention. But if we had a contract for the handler methods, it would make it impossible to do some of the things it’s doing. Features that I personally really like.

GitHub - FoundatioFx/Foundatio.Mediator: High-performance C# mediator library with source generators and minimal boilerplate High-performance C# mediator library with source generators and minimal boilerplate - FoundatioFx/Foundatio.Mediator

github.com/FoundatioFx/...

I've been working on something cool - Foundatio.Mediator! It's a blazingly fast, convention-based C# mediator that uses source generators and interceptors.

✨ Near-direct method call performance
⚡ Zero runtime reflection
🔧 Convention over configuration
🎯 Built-in Result<T> pattern

Thoughts? 🤔