[lewisrenfrew]

Adds JsonMessageHandler< T > which is the consuming-side counterpart to JsonMessagePublisher< T >. It uses the Template Method pattern to handle deserialization internally and then invoke your custom handler code, which now only has to deal with strongly-typed objects.

So when writing a new handler, instead of implementing the raw IMessageHandler directly and having to call some code to deserialize bytes, just inherit from this new JsonMessageHandler< T > and override the typed HandleAsync.

For example

public class OrderCreatedHandler : JsonMessageHandler<Order>
{

    protected override Task HandleAsync(
        Order payload,
        IReadOnlyDictionary<string, object> headers,
        CancellationToken cancellationToken)
    {
     // payload is already deserialized - just do your thing in here
    }
}

[lewisrenfrew]

Adds JsonMessageHandler< T > which is the consuming-side counterpart to JsonMessagePublisher< T >. It uses the Template Method pattern to handle deserialization internally and then invoke your custom handler code, which now only has to deal with strongly-typed objects.

So when writing a new handler, instead of implementing the raw IMessageHandler directly and having to call some code to deserializing bytes, just inherit from this new JsonMessageHandler< T > and override the typed HandleAsync.

For example

public class OrderCreatedHandler : JsonMessageHandler<Order>
{

    protected override Task HandleAsync(
        Order payload,
        IReadOnlyDictionary<string, object> headers,
        CancellationToken cancellationToken)
    {
     // payload is already deserialized - just do your thing in here
    }
}

oh and you can still write non json handlers as before by just using the base IMesageHandler if you ever need to... although I expect cases where JSON deserializiation is not required be few and far between, if not non-existent