IGet 1.0.4

IGet

Say goodbye to MediatR's IRequest-IRequestHandler combination and use IGet instead: less code, more freedom.

serviceCollection.AddIGet();

Why?

You're probably very happy with how MediatR solves injecting dependencies into your IRequestHandler implementations. You might however like IGet better as a simpler alternative for the IRequest-IRequestHandler combination:

• you don't need to implement any interface for your handlers.
• creating a request class is optional.
• have compile-time checks that all handlers exist.
• use editor-shortcuts to jump to a handler method immediately.
• have a shorter StackTrace in case of an error.
• etc.

IGet is not a replacement for - for example - INotifications and it does not have things like IRequestPostProcessors. It just instantiates a class with its dependencies injected.

Declaring a handler

Example 1

public class MyHandler
{
    private ILogger<MyHandler> _logger;

    public MyHandler(ILogger<MyHandler> logger)
    {
        _logger = logger;
    }

    public MyResult AnyRandomSignature(int id)
    {
        // do something
    }
}

Example 2

public class MyHandler
{
    private ILogger<MyHandler> _logger;

    public MyHandler(ILogger<MyHandler> logger)
    {
        _logger = logger;
    }

    public void Handle()
    {
        // do something
    }
}

Sending a request

In the examples below i is the IGet instance where you call Get on. (Like mediator might have been the name of the variable for a IMediator instance where you called Send on.)

Example 1

var result = i.Get<MyHandler>().AnyRandomSignature(1);

Example 2

var result = await i.Get<MyHandler>().HandleAsync(new MyOtherRequest
{
    Id = 2
});

Example 3

var result = i.Get<MyHandler>().Handle();

Example 4

var handler = i.Get<MyHandler>();
var result = handler.Handle();

etc.

Can IGet and MediatR be used together?

Yes. There is no need to replace old code.