IGet 1.0.3

IGet

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

serviceCollection.AddIGet();

Using IGet

MediatR requires declarations like this:

public class MyRequest : IRequest<MyResult>
{
    public int Id { get; set; }
}

public class MyHandler : IRequestHandler<MyRequest, MyResult>
{
    private ILogger<MyHandler> _logger;

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

    public async Task<MyResult> Handle(MyRequest request, CancellationToken cancellationToken)
    {
        // do something
    }
}

IGet allows you to use the simplest possible declaration:

public class MyHandler
{
    private ILogger<MyHandler> _logger;

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

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

With IMediator you don't have compile time checks that a handler exists:

var result = await _mediator.Send(new MyRequestWithoutHandler { Id = 1 });

With IGet you have immediate verification that the handler exists in scope:

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

Can IGet and MediatR be used together?

Yes. There is no need to replace old code.