Merge pull request #554 from TimeWarpEngineering/Cramer/2025-08-12/032migrate-from-mediatr-to-timewarp-mediator

Task 032: Migrate from MediatR to TimeWarp.Mediator

Author: StevenTCramer

.ai/other/nugets.md

@@ -1,7 +1,7 @@
 ---
 nuget_categories:
   General:
-    - name: MediatR
+    - name: TimeWarp.Mediator
       for: CQRS and mediator pattern
     - name: Riok.Mapperly
       for: object-object mapping

.ai/other/references.md

@@ -33,11 +33,10 @@ references:
     resources:
       - Official Documentation: https://playwright.dev/dotnet/docs/intro
 
-  - name: MediatR NuGet Library
+  - name: TimeWarp.Mediator NuGet Library
     relationship: Used extensively by TimeWarp.State
     resources:
-      - Official Documentation: https://github.com/jbogard/MediatR/wiki
-      - Authors Blog: https://www.jimmybogard.com/
+      - Official Repository: https://github.com/TimeWarpEngineering/timewarp-mediator
 
   - name: AnyClone NuGet Library
     relationship: Used as the default cloning ability if ICloneable has not been implemented.

Claude.md

@@ -4,7 +4,7 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co
 
 ## Project Overview
 
-**TimeWarp.State** is a state management library for Blazor applications implementing the Flux pattern using MediatR pipeline. It handles both client-side (WebAssembly) and server-side Blazor with async state management.
+**TimeWarp.State** is a state management library for Blazor applications implementing the Flux pattern using Mediator pipeline. It handles both client-side (WebAssembly) and server-side Blazor with async state management.
 
 ## Development Commands
 
@@ -74,7 +74,7 @@ dotnet build --project <ProjectPath> --configuration Release
 
 ### Key Patterns
 - **CQRS/Flux**: Unidirectional data flow with Actions/ActionHandlers
-- **MediatR Pipeline**: Middleware-driven architecture
+- **TimeWarp.Mediator Pipeline**: Middleware-driven architecture
 - **Async-First**: All operations are async by design
 - **TypeScript Integration**: Strong typing for JavaScript interop
 
@@ -163,7 +163,7 @@ Follow structured task workflow using Kanban approach:
 ## Essential Dependencies
 
 - **Blazor**: UI framework (Server/WebAssembly)
-- **MediatR**: CQRS/mediator pattern implementation
+- **TimeWarp.Mediator**: CQRS/mediator pattern implementation
 - **Microsoft.JSInterop**: JavaScript interop for browser features
 - **Fixie**: Testing framework
 - **NetArchTest**: Architecture testing

Directory.Build.props

@@ -1,12 +1,12 @@
 <Project>
   <!-- Set common properties regarding assembly information and nuget packages -->
   <PropertyGroup>
-    <TimeWarpStateVersion>11.0.3</TimeWarpStateVersion>
+    <TimeWarpStateVersion>12.0.0-beta.1</TimeWarpStateVersion>
     <Authors>Steven T. Cramer</Authors>
     <Product>TimeWarp State</Product>
     <PackageVersion>$(TimeWarpStateVersion)</PackageVersion>
     <PackageProjectUrl>https://timewarpengineering.github.io/timewarp-state/</PackageProjectUrl>
-    <PackageTags>TimeWarp.State; TimeWarp-State; TimeWarpState; BlazorState; Blazor; State; Blazor-State; MediatR; Mediator; Pipeline; Redux; Flux</PackageTags>
+    <PackageTags>TimeWarp.State; TimeWarp-State; TimeWarpState; BlazorState; Blazor; State; Blazor-State; MediatR; Mediator; TimeWarp.Mediator; Pipeline; Redux; Flux</PackageTags>
     <PackageIcon>Logo.png</PackageIcon>
     <RepositoryUrl>https://github.com/TimeWarpEngineering/timewarp-state.git</RepositoryUrl>
     <RepositoryType>git</RepositoryType>

Directory.Packages.props

@@ -9,7 +9,7 @@
     <PackageVersion Include="Fixie.TestAdapter" Version="3.4.0" />
     <PackageVersion Include="FluentAssertions" Version="6.12.1" />
     <PackageVersion Include="JetBrains.Annotations" Version="2024.2.0" />
-    <PackageVersion Include="MediatR" Version="12.4.1" />
+    <PackageVersion Include="TimeWarp.Mediator" Version="13.0.0" />
     <PackageVersion Include="Microsoft.AspNetCore.Components.Web" Version="8.0.17" />
     <PackageVersion Include="Microsoft.AspNetCore.Components.WebAssembly" Version="8.0.17" />
     <PackageVersion Include="Microsoft.AspNetCore.Components.WebAssembly.DevServer" Version="8.0.17" />

Documentation/Images/TimeWarpStateOneWayFlow.drawio

@@ -88,7 +88,7 @@
         <mxCell id="pQi_TNxkMac2TIVI0rjQ-33" value="" style="shape=curlyBracket;whiteSpace=wrap;html=1;rounded=1;labelPosition=left;verticalLabelPosition=middle;align=left;verticalAlign=middle;" vertex="1" parent="1">
           <mxGeometry x="110" y="280" width="20" height="440" as="geometry" />
         </mxCell>
-        <mxCell id="pQi_TNxkMac2TIVI0rjQ-36" value="MediatR Pipeline" style="text;html=1;align=center;verticalAlign=middle;resizable=0;points=[];autosize=1;strokeColor=none;fillColor=none;" vertex="1" parent="1">
+        <mxCell id="pQi_TNxkMac2TIVI0rjQ-36" value="Mediator Pipeline" style="text;html=1;align=center;verticalAlign=middle;resizable=0;points=[];autosize=1;strokeColor=none;fillColor=none;" vertex="1" parent="1">
           <mxGeometry y="485" width="110" height="30" as="geometry" />
         </mxCell>
         <mxCell id="pQi_TNxkMac2TIVI0rjQ-42" value="SubscriptionNotification" style="text;html=1;align=center;verticalAlign=middle;resizable=0;points=[];autosize=1;strokeColor=none;fillColor=none;" vertex="1" parent="1">

Documentation/Images/TimeWarpStateOneWayFlow.drawio.svg

@@ -37,7 +37,7 @@ or move the GetState functionality into your component
 
 ### Pipeline
 
-**TimeWarp.State** utilizes the MediatR pipeline which allows for middleware integration
+**TimeWarp.State** utilizes the TimeWarp.Mediator pipeline which allows for middleware integration
 by registering an interface with the dependency injection container [^4].
 TimeWarp.State provides the extension method [^5] , `AddTimeWarpState`, which registers behaviors on the pipeline.
 
@@ -94,7 +94,7 @@ if the developer chose they could mark the Requests as such. For example **IActi
 
 #### Footnotes:
 
-[^1]: https://github.com/jbogard/MediatR
+[^1]: https://github.com/TimeWarpEngineering/timewarp-mediator
 
 [^2]: https://redux.js.org/
 

Documentation/Overview.md

@@ -5,18 +5,12 @@ title: Acknowledgements
 
 ## Acknowledgements
 
-Jimmy Bogard ([MediatR](https://github.com/jbogard/MediatR)).
-Jimmy is an amazing developer and knowledge sharer.  
-Through his course at [11x Engieering](https://11xengineering.com/),
-his many blog posts on Los Techies and now [JimmyBogard.com](https://jimmybogard.com/),
-I have learned a great amount.
-
 Peter Morris and I have been friends for many years.
 He is an amazing developer and a person who has taught me a great deal.
-Not surprisingly, Pete and I think a lot alike.
+Not surprisingly, Pete and I think a lot a like.
 We both, independently, started working on our own State Management
 components. Although I started first. :P
 Pete's component attempts to solve most of the same problems.
-TimeWarp.State draws on the strengths of a proven async pipeline in MediatR, where as Fluxor
+TimeWarp.State draws on the strengths of a proven async pipeline in Mediator, where as Fluxor
 implements its own middleware.  
 If TimeWarp.State does not meet your needs be sure to checkout Fluxor.

Documentation/Partials/Acknowledgements.md

@@ -7,11 +7,11 @@ title: Summary
 
 **TimeWarp.State** (previously known as Blazor-State [![nuget](https://img.shields.io/nuget/dt/Blazor-State?logo=nuget)](https://www.nuget.org/packages/Blazor-State/) ) 
 is a fully asynchronous state management library for Blazor applications,
-leveraging the MediatR pipeline to implement the Flux pattern. 
+leveraging the Mediator pipeline to implement the Flux pattern. 
 It handles both Reducers and Effects consistently using async Handlers,
 simplifying the management of asynchronous operations throughout your app.
 
-By utilizing the MediatR pipeline, TimeWarp.State enables a flexible, 
+By utilizing the Mediator pipeline, TimeWarp.State enables a flexible, 
 middleware-driven architecture for managing state, 
 similar to the request-processing pipeline in ASP.NET. 
 This approach allows developers to inject custom behaviors, such as logging,