Shiny.Mediator 1.0.0-alpha-0025

Prefix Reserved
This is a prerelease version of Shiny.Mediator.
There is a newer version of this package available.
See the version list below for details.
dotnet add package Shiny.Mediator --version 1.0.0-alpha-0025                
NuGet\Install-Package Shiny.Mediator -Version 1.0.0-alpha-0025                
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Shiny.Mediator" Version="1.0.0-alpha-0025" />                
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add Shiny.Mediator --version 1.0.0-alpha-0025                
#r "nuget: Shiny.Mediator, 1.0.0-alpha-0025"                
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install Shiny.Mediator as a Cake Addin
#addin nuget:?package=Shiny.Mediator&version=1.0.0-alpha-0025&prerelease

// Install Shiny.Mediator as a Cake Tool
#tool nuget:?package=Shiny.Mediator&version=1.0.0-alpha-0025&prerelease                

Shiny Mediator (Preview)

PLEASE NOTE - THIS IS AN ALPHA. THINGS ARE LIKELY TO CHANGE

<a href="https://www.nuget.org/packages/Shiny.Mediator" target="_blank"> <img src="https://buildstats.info/nuget/Shiny.Mediator?includePreReleases=true" /> </a>

A mediator pattern, but for apps. Apps have pages with lifecycles that don't necessarily participate in the standard dependency injection lifecycle. .NET MAUI generally tends to favor the Messenger pattern. We hate this pattern for many reasons which we won't get into. That being said, we do offer a messenger subscription in our Mediator for where interfaces and dependency injection can't reach.

This project is heavily inspired by MediatR with some lesser features that we feel were aimed more at server scenarios, while also adding some features we feel benefit apps

Features

  • A Mediator for your .NET Apps (MAUI & Blazor are the main targets for us)
  • Think of "weak" message subscriptions without the fuss or mess to cleanup
  • Our MAUI & Blazor integrations allow your viewmodels or pages to implement an IEventHandler<TEvent> interface(s) without them having to participate in the dependency injection provider
  • We still have a "messagingcenter" type subscribe off IMediator for cases where you can't have your current type implement an interface
  • Instead of Assembly Scanning, we have source generators to automatically wireup the necessary registrations for you! (WIP)
  • Lightweight, No external dependencies, tiny bit of reflection
  • Help remove service overrun and reduce your constructor fat
  • Easy to Unit Test

Works With

  • .NET MAUI - all platforms
  • MVVM Frameworks like Prism, ReactiveUI, & .NET MAUI Shell
  • Blazor - TBD
  • Any other .NET platform - but you'll have to come up with your own "event collector" for the out-of-state stuff

Getting Started

Install Shiny.Mediator from NuGet

First, let's create our request & event handlers

using Shiny.Mediator;

public record TestRequest(string AnyArgs, int YouWant) : IRequest;
public record TestEvent(MyObject AnyArgs) : IEvent;

// and for request/response requests - we'll come back to this
public record TestResponseRequest : IRequest<TestResponse> {}
public record TestResponse {}

Next - let's wire up a RequestHandler. You can have ONLY 1 request handler per request type. This is where you would do the main business logic or data requests.

Let's create our RequestHandler

using Shiny.Mediator;

// NOTE: Request handlers are registered as singletons
public class TestRequestHandler : IRequestHandler<TestRequest> 
{
    // you can do all dependency injection here
    public async Task Handle(TestRequest request, CancellationToken ct) 
    {
        // do something async here
    }
}

public class TestResponseRequestHandler : IRequestHandler<TestResponseRequest, TestResponse>
{
    public async Task<TestResponse> Handle(TestResponseRequest request, CancellationToken ct)
    {
        var response = await GetResponseThing(ct);
        return response;
    }
}

public class TestEventHandler : IEventHandler<TestEvent> 
{
    // Dependency injection works here
    public async Task Handle(TestEvent @event, CancellationToken ct)
    {
        // Do something async here
    }
}

Now, let's register all of our stuff with our .NET MAUI MauiProgram.cs

public static class MauiProgram
{
    public static MauiApp CreateMauiApp()
    {
        var builder = MauiApp
            .CreateBuilder()
            .UseMauiApp<App>();
        
        builder.Services.AddShinyMediator();
        builder.Services.AddSingletonAsImplementedInterfaces<TestEventHandler>();
        builder.Services.AddSingletonAsImplementedInterfaces<TestRequestHandler>();
        builder.Services.AddSingltonAsImplementedInterfaces<TestResponseRequestHandler>();
        // OR if you're using our attribute for source generation
    }
}

Lastly, any model model/viewmodel/etc participating in dependency injection can now inject the mediator

public class MyViewModel(Shiny.Mediator.IMediator mediator)
{
    public async Task Execute() 
    {
        await mediator.Send(new TestRequest()); // this will execute TestRequestHandler
        var response = await mediator.Send(new TestResponseRequest()); // this will execute TestResponseRequestHandler and return a value
        
        // this will publish to any service registered that implement IEventHandler<TestEvent>
        // there are additional args here to allow you to execute values in sequentially or wait for all events to complete
        await mediator.Publish(new TestEvent()); 
    }
}

What about my ViewModels?

For .NET MAUI, your viewmodels have the ability to participate in the event publishing chain without being part of dependency injection

With this setup, you don't need to worry about deallocating any events, unsubscribing from some service, or hooking to anything.

Lastly, if your page/viewmodel is navigated away from (popped), it will no longer participate in the event broadcast

First, let's install Shiny.Mediator.Maui Now...let's go back to our MauiProgram.cs and alter the AddShinyMediator

builder.Services.AddShinyMediator<MauiEventCollector>();

Now your viewmodel (or page) can simply implement the IEventHandler<T> interface to participate

NOTE: Further example to below - you can implement multiple event handlers (or request handlers)

public class MyViewModel : BaseViewModel, 
                           Shiny.Mediator.IEventHandler<TestEvent>,
                           Shiny.Mediator.IEventHandler<TestEvent>
{
    public async Task Handle(TestEvent @event, CancellationToken ct)
    {
    }
    
    public async Task Handle(TestEvent2 @event, CancellationToken ct)
    {
    }
}

Request Middleware

TODO

Event Covariance

TODO

Sample

There is a sample in this repo. You do not need any other part of Shiny, Prism, ReactiveUI, etc - those are included as I write things faster with it. Focus on the interfaces from the mediator & the mediator calls itself

Ideas for Workflows

  • Use Prism with Modules - want strongly typed navigation parameters, navigations, and have them available to other modules - we're the guy to help!
    • Example TBD
  • Using a Shiny Foreground Job - want to push data an event that new data came in to anyone listening?
  • Have a Shiny Push Delegate that is executing on the delegate but want to push it to the UI, Mediator has a plan!

Request Middleware Ideas

  • Connectivity check - pull from cache/memory or go to the API

TODO

  • Explain Event Collectors
  • Event Collectors for MAUI execute on main thread?
  • Streams - IAsyncEnumerable or IObservable
  • Source Generator Registration
    • Need to use a different method or not use extension methods - maybe AddHandlersFromAssemblyName or allow it to be custom named
  • IEventHandler<IEvent> can handle ALL events?
Product Compatible and additional computed target framework versions.
.NET net8.0 is compatible.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (8)

Showing the top 5 NuGet packages that depend on Shiny.Mediator:

Package Downloads
Shiny.Mediator.Maui

Shiny Mediator - A mediator pattern for all .NET Apps

Shiny.Mediator.Blazor

Shiny Mediator - A mediator pattern for all .NET Apps

Shiny.Mediator.Resilience

Shiny Mediator - A mediator pattern for all .NET Apps

Shiny.Mediator.Caching

Shiny Mediator - A mediator pattern for all .NET Apps

Shiny.Mediator.Prism

Shiny Mediator - A mediator pattern for all .NET Apps

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
2.2.0-beta-0001 127 10/28/2024
2.1.1 212 10/28/2024
2.1.0 222 10/19/2024
2.1.0-beta-0016 117 10/19/2024
2.1.0-beta-0015 120 10/19/2024
2.1.0-beta-0014 135 10/19/2024
2.1.0-beta-0013 130 10/19/2024
2.1.0-beta-0011 145 10/18/2024
2.1.0-beta-0010 139 10/18/2024
2.1.0-beta-0004 120 10/8/2024
2.1.0-beta-0002 116 10/6/2024
2.0.2 385 10/6/2024
2.0.1 138 10/6/2024
2.0.0 190 10/4/2024
2.0.0-beta-0060 116 10/6/2024
2.0.0-beta-0059 112 10/6/2024
2.0.0-beta-0056 114 10/4/2024
2.0.0-beta-0054 124 10/3/2024
2.0.0-beta-0053 121 10/2/2024
2.0.0-beta-0052 126 10/2/2024
2.0.0-beta-0050 120 10/2/2024
2.0.0-beta-0049 128 10/2/2024
2.0.0-beta-0046 130 10/1/2024
2.0.0-beta-0044 119 9/30/2024
2.0.0-beta-0026 131 9/24/2024
2.0.0-beta-0023 120 9/23/2024
2.0.0-beta-0022 106 9/23/2024
2.0.0-beta-0020 116 9/22/2024
2.0.0-beta-0004 119 9/20/2024
2.0.0-beta-0003 129 9/20/2024
1.9.0-beta-0003 129 9/16/2024
1.9.0-beta-0001 135 9/15/2024
1.9.0-beta 134 9/15/2024
1.8.1 314 9/14/2024
1.8.1-beta-0006 128 9/14/2024
1.8.1-beta-0005 137 9/14/2024
1.8.1-beta-0004 128 9/14/2024
1.8.1-beta-0003 133 9/14/2024
1.8.1-beta-0002 132 9/14/2024
1.8.1-beta-0001 136 9/14/2024
1.8.0 182 9/12/2024
1.8.0-beta-0064 136 9/12/2024
1.8.0-beta-0063 155 9/12/2024
1.8.0-beta-0059 136 9/8/2024
1.8.0-beta-0058 130 9/8/2024
1.8.0-beta-0057 139 9/8/2024
1.8.0-beta-0054 157 9/7/2024
1.8.0-beta-0053 155 9/6/2024
1.8.0-beta-0052 144 9/6/2024
1.8.0-beta-0051 148 9/6/2024
1.8.0-beta-0044 155 9/5/2024
1.8.0-beta-0042 146 9/4/2024
1.8.0-beta-0041 140 9/4/2024
1.8.0-beta-0027 165 8/25/2024
1.8.0-beta-0022 161 8/23/2024
1.8.0-beta-0017 139 8/7/2024
1.8.0-beta-0012 98 7/28/2024
1.8.0-beta-0010 88 7/28/2024
1.7.5 203 8/23/2024
1.7.4 211 8/9/2024
1.7.3 162 8/7/2024
1.7.2 123 7/28/2024
1.7.1 103 7/28/2024
1.7.0 161 7/20/2024
1.7.0-beta-0005 115 7/20/2024
1.7.0-beta-0001 127 7/8/2024
1.6.0 167 7/8/2024
1.6.0-beta-0004 118 7/7/2024
1.5.0 148 7/6/2024
1.5.0-beta-0010 128 7/6/2024
1.5.0-beta-0006 119 7/4/2024
1.4.5 140 7/4/2024
1.4.2 147 6/30/2024
1.4.1 145 6/30/2024
1.4.0 144 6/30/2024
1.4.0-beta-0010 136 6/30/2024
1.3.1 134 6/29/2024
1.3.0 135 6/29/2024
1.3.0-beta-0014 118 6/29/2024
1.3.0-beta-0007 113 6/26/2024
1.2.0 138 6/20/2024
1.2.0-beta-0001 98 6/20/2024
1.1.0 128 6/17/2024
1.1.0-beta-0019 114 6/20/2024
1.1.0-beta-0016 118 6/19/2024
1.1.0-beta-0014 129 6/17/2024
1.1.0-beta-0013 129 6/17/2024
1.0.0 142 6/15/2024
1.0.0-alpha-0054 123 6/15/2024
1.0.0-alpha-0053 121 6/12/2024
1.0.0-alpha-0051 105 6/12/2024
1.0.0-alpha-0048 114 6/10/2024
1.0.0-alpha-0047 123 6/10/2024
1.0.0-alpha-0043 111 6/9/2024
1.0.0-alpha-0042 136 6/7/2024
1.0.0-alpha-0040 121 6/6/2024
1.0.0-alpha-0038 116 6/6/2024
1.0.0-alpha-0036 106 6/5/2024
1.0.0-alpha-0034 130 6/4/2024
1.0.0-alpha-0031 114 6/4/2024
1.0.0-alpha-0025 114 6/3/2024
1.0.0-alpha-0023 121 6/2/2024
1.0.0-alpha-0022 123 6/1/2024
1.0.0-alpha-0019 118 6/1/2024
1.0.0-alpha-0018 106 6/1/2024
1.0.0-alpha-0014 121 6/1/2024
1.0.0-alpha-0013 103 6/1/2024
1.0.0-alpha-0012 109 5/31/2024
1.0.0-alpha-0011 104 5/31/2024
1.0.0-alpha-0010 109 5/31/2024