MVC client consuming Web API with MediatR implementation about mediatr HOT 1 CLOSED

If MVC calls WebApi, it's just a regular restful api call. It has to follow whatever the api exposed.

On the Api side, you do have a choice of exposing MediatR request, or use primitive type. With request, it's easier to validate and you can pass request directly to handler. But you could end up with some ridiculous request like UserIdRequest { int Id } . It also forces some non-restful convention onto consumers, I think.

If you expose primitive type, like User (int id), the interface is more natural. But you have to manually create request before send. There also seems no easy way to validate primitive type on controller method.

Most updates are probably done using Post with complex type, in that case, you do expose MediatR request. You can share dll, create documentation, generate proxy class, etc.

I really wish the framework can automatically wire up all requests as controllers though, save tons of boilerplate work.

from mediatr.