Shiny.Mediator.Blazor 3.0.0-beta-0046

Shiny Mediator

<a href="https://www.nuget.org/packages/Shiny.Mediator" target="_blank"> <img src="https://img.shields.io/nuget/v/Shiny.Mediator?style=for-the-badge" /> </a>

Mediator is a behavioral design pattern that lets you reduce chaotic dependencies between objects. The pattern restricts direct communications between the objects and forces them to collaborate only via a mediator object.

Shiny Mediator is a mediator pattern implementation, works for server, but also works great 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

Links

• Docs
  • Main
  • Quick Start
• Sample
• End-to-End Architectural Layout Sample
• A Cool Offline Capable App with Mediator and Shiny

Features

• A Mediator for your .NET Apps (ASP.NET, Blazor, MAUI, basically anywhere in .NET)
• Request/Response "Command" Handling
• Event Publication
• Request & event middleware with some great "out of the box" scenarios for your app
• 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 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
• Direct Handler to ASP.NET Core endpoint
• OpenAPI Contract & Handler Generation
• Epic Out-of-the-Box Middleware
  • Offline Storage
  • Validation with Data Annotations or FluentValidation
  • Caching
  • Resiliency
  • User Exception Handling notifications
  • Exception Handling logging
  • Performance Time Logging
  • Main Thread Dispatching
  • Replayable Streams
  • Refresh Timer Streams
  • Registration straight from startup to mediator (we do the minimal api reg for you)

Works With

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