Shiny.Mediator.Blazor 1.0.0-alpha-0018

Prefix Reserved
This is a prerelease version of Shiny.Mediator.Blazor.
There is a newer version of this package available.
See the version list below for details.
dotnet add package Shiny.Mediator.Blazor --version 1.0.0-alpha-0018                
NuGet\Install-Package Shiny.Mediator.Blazor -Version 1.0.0-alpha-0018                
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.Blazor" Version="1.0.0-alpha-0018" />                
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add Shiny.Mediator.Blazor --version 1.0.0-alpha-0018                
#r "nuget: Shiny.Mediator.Blazor, 1.0.0-alpha-0018"                
#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.Blazor as a Cake Addin
#addin nuget:?package=Shiny.Mediator.Blazor&version=1.0.0-alpha-0018&prerelease

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

Shiny Mediator (Preview)

<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.

Features

  • A Mediator for your .NET Apps (MAUI & Blazor are the main targets for us)
  • Think of "weak" message subscription without the fuss or mess to cleanup
  • Fire & Forget as well as Parallel Event execution
  • 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!
  • 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
        // by default, publish calls are "fire & forget" under the hood and execute in parallel
        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

Let's go back to 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)
    {
    }
}

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!

TODO

  • Pipelines
    • Error handlers - requests and events?
    • Pre/Post Execution - Time how long events took, time how long a command took
  • Explain Event Handlers
  • Streams - IAsyncEnumerable or IObservable
  • Source Generator Registration
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

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
2.2.0-beta-0001 59 10/28/2024
2.1.1 68 10/28/2024
2.1.0 88 10/19/2024
2.1.0-beta-0016 62 10/19/2024
2.1.0-beta-0015 61 10/19/2024
2.1.0-beta-0014 73 10/19/2024
2.1.0-beta-0013 73 10/19/2024
2.1.0-beta-0011 92 10/18/2024
2.1.0-beta-0010 88 10/18/2024
2.1.0-beta-0004 61 10/8/2024
2.1.0-beta-0002 56 10/6/2024
2.0.2 84 10/6/2024
2.0.1 82 10/6/2024
2.0.0 76 10/4/2024
2.0.0-beta-0060 65 10/6/2024
2.0.0-beta-0059 61 10/6/2024
2.0.0-beta-0056 58 10/4/2024
2.0.0-beta-0054 74 10/3/2024
2.0.0-beta-0053 63 10/2/2024
2.0.0-beta-0052 66 10/2/2024
2.0.0-beta-0050 73 10/2/2024
2.0.0-beta-0049 64 10/2/2024
2.0.0-beta-0046 66 10/1/2024
2.0.0-beta-0044 66 9/30/2024
2.0.0-beta-0026 73 9/24/2024
2.0.0-beta-0023 60 9/23/2024
2.0.0-beta-0022 49 9/23/2024
2.0.0-beta-0020 57 9/22/2024
2.0.0-beta-0004 53 9/20/2024
2.0.0-beta-0003 70 9/20/2024
1.9.0-beta-0003 69 9/16/2024
1.9.0-beta-0001 63 9/15/2024
1.9.0-beta 67 9/15/2024
1.8.1 90 9/14/2024
1.8.1-beta-0006 65 9/14/2024
1.8.1-beta-0005 77 9/14/2024
1.8.1-beta-0004 64 9/14/2024
1.8.1-beta-0003 54 9/14/2024
1.8.1-beta-0002 84 9/14/2024
1.8.1-beta-0001 64 9/14/2024
1.8.0 120 9/12/2024
1.8.0-beta-0064 80 9/12/2024
1.8.0-beta-0063 89 9/12/2024
1.8.0-beta-0059 65 9/8/2024
1.8.0-beta-0058 72 9/8/2024
1.8.0-beta-0057 81 9/8/2024
1.8.0-beta-0054 88 9/7/2024
1.8.0-beta-0053 81 9/6/2024
1.8.0-beta-0052 80 9/6/2024
1.8.0-beta-0051 90 9/6/2024
1.8.0-beta-0044 95 9/5/2024
1.8.0-beta-0042 78 9/4/2024
1.8.0-beta-0041 67 9/4/2024
1.8.0-beta-0027 101 8/25/2024
1.8.0-beta-0022 93 8/23/2024
1.8.0-beta-0017 69 8/7/2024
1.8.0-beta-0012 62 7/28/2024
1.8.0-beta-0010 62 7/28/2024
1.7.5 117 8/23/2024
1.7.4 109 8/9/2024
1.7.3 85 8/7/2024
1.7.2 74 7/28/2024
1.7.1 62 7/28/2024
1.7.0 111 7/20/2024
1.7.0-beta-0005 87 7/20/2024
1.7.0-beta-0001 75 7/8/2024
1.6.0 97 7/8/2024
1.6.0-beta-0004 79 7/7/2024
1.5.0 96 7/6/2024
1.5.0-beta-0010 89 7/6/2024
1.5.0-beta-0006 84 7/4/2024
1.4.5 108 7/4/2024
1.4.2 102 6/30/2024
1.4.1 100 6/30/2024
1.4.0 95 6/30/2024
1.4.0-beta-0010 85 6/30/2024
1.3.1 104 6/29/2024
1.3.0 97 6/29/2024
1.3.0-beta-0014 86 6/29/2024
1.3.0-beta-0007 75 6/26/2024
1.2.0 106 6/20/2024
1.2.0-beta-0001 85 6/20/2024
1.1.0 95 6/17/2024
1.1.0-beta-0019 84 6/20/2024
1.1.0-beta-0016 88 6/19/2024
1.1.0-beta-0014 91 6/17/2024
1.1.0-beta-0013 83 6/17/2024
1.0.0 105 6/15/2024
1.0.0-alpha-0054 89 6/15/2024
1.0.0-alpha-0053 81 6/12/2024
1.0.0-alpha-0051 90 6/12/2024
1.0.0-alpha-0048 89 6/10/2024
1.0.0-alpha-0047 85 6/10/2024
1.0.0-alpha-0043 90 6/9/2024
1.0.0-alpha-0042 99 6/7/2024
1.0.0-alpha-0040 97 6/6/2024
1.0.0-alpha-0038 95 6/6/2024
1.0.0-alpha-0036 97 6/5/2024
1.0.0-alpha-0034 99 6/4/2024
1.0.0-alpha-0031 91 6/4/2024
1.0.0-alpha-0025 93 6/3/2024
1.0.0-alpha-0023 88 6/2/2024
1.0.0-alpha-0022 91 6/1/2024
1.0.0-alpha-0019 85 6/1/2024
1.0.0-alpha-0018 89 6/1/2024
1.0.0-alpha-0014 103 6/1/2024
1.0.0-alpha-0013 87 6/1/2024
1.0.0-alpha-0012 87 5/31/2024
1.0.0-alpha-0011 95 5/31/2024
1.0.0-alpha-0010 96 5/31/2024