Fix remaining MediatR references in comments and documentation

StevenTCramer · claude · StevenTCramer · commit c847bdbdd90d · 2025-08-19T16:31:17.000+07:00
- Update XML comments to reference Mediator instead of MediatR - Fix analyzer test to use TimeWarp.Mediator.Contracts.dll - Update SVG diagram to replace MediatR with Mediator - Clean up all remaining textual references to MediatR 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
diff --git a/.ai/other/nugets.md b/.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
diff --git a/.ai/other/references.md b/.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.
diff --git a/Claude.md b/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
diff --git a/Directory.Build.props b/Directory.Build.props
@@ -6,7 +6,7 @@
     <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>
diff --git a/Documentation/Images/TimeWarpStateOneWayFlow.drawio b/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">
diff --git a/Documentation/Images/TimeWarpStateOneWayFlow.drawio.svg b/Documentation/Images/TimeWarpStateOneWayFlow.drawio.svg
diff --git a/Documentation/Overview.md b/Documentation/Overview.md
@@ -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/
 
diff --git a/Documentation/Partials/Acknowledgements.md b/Documentation/Partials/Acknowledgements.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.
diff --git a/Documentation/Partials/Summary.md b/Documentation/Partials/Summary.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,
diff --git a/Documentation/Partials/Terminology.md b/Documentation/Partials/Terminology.md
@@ -5,15 +5,15 @@ title: Terminology
 
 ## Terminology
 
-The pattern used by TimeWarp.State and MediatR has been around for many years and goes by different names.
+The pattern used by TimeWarp.State and TimeWarp.Mediator have been around for many years and goes by different names.
 We list various related terms here and **Bold** indicates the term used in TimeWarp.State.
 
 ### Signals/**Actions**/**Requests**/Commands/
 
 In Redux they call them "Action".  
 In UML they are "Signal".  
 In Command Pattern they are "Command"  
-In MediatR they are `Request`
+In Mediator they are `Request`
 In TimeWarp.State we call them `Actions` when they are handled on the Client and `Requests` if they handled on the Server.
 
 ### Reducer/**Handler**/Executor
@@ -22,7 +22,7 @@ This is the code that processes the `Request/Action` and returns the `Response`.
 
 In Redux they call them "Reducer".
 In Command Pattern we call them "Executor".  
-In MediatR they are `Handler`.  
+In Mediator they are `Handler`.  
 In TimeWarp.State we call them `Handler`.
 
 ### Feature
diff --git a/README.md b/README.md
@@ -20,9 +20,9 @@
 
 # TimeWarp.State
 
-**TimeWarp.State** (previously known as Blazor-State) is a fully asynchronous state management library for Blazor applications, leveraging the MediatR 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.
+**TimeWarp.State** (previously known as Blazor-State) is a fully asynchronous state management library for Blazor applications, leveraging the res 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, 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, validation, and caching, directly into the state management flow.
+By utilizing the TimeWarp.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, validation, and caching, directly into the state management flow.
 
 In addition to the core library, we offer **[TimeWarp.State.Plus](/Source/TimeWarp.State.Plus)**, which extends the functionality with enhanced middleware, components, and tools to further streamline state management in complex Blazor applications.
 
diff --git a/Source/TimeWarp.State/Extensions/ServiceCollectionExtensions.LogTimeWarpStateMiddleware.cs b/Source/TimeWarp.State/Extensions/ServiceCollectionExtensions.LogTimeWarpStateMiddleware.cs
@@ -8,7 +8,7 @@ public static void LogTimeWarpStateMiddleware(this IServiceCollection serviceCol
     List<string> middleware = GetComponentOrder(serviceCollection, typeof(IPipelineBehavior<,>));
     List<string> postprocessors = GetComponentOrder(serviceCollection, typeof(IRequestPostProcessor<,>));
 
-    var message = new StringBuilder("TimeWarp State (MediatR) Middleware Registrations:");
+    var message = new StringBuilder("TimeWarp State (TimeWarp.Mediator) Middleware Registrations:");
     message.AppendLine();
     message.AppendLine();
     
diff --git a/Source/TimeWarp.State/Extensions/TimeWarpStateOptions.cs b/Source/TimeWarp.State/Extensions/TimeWarpStateOptions.cs
@@ -6,7 +6,7 @@ namespace TimeWarp.State;
 public class TimeWarpStateOptions
 {
   /// <summary>
-  /// Assemblies to be searched for MediatR Actions and Handlers
+  /// Assemblies to be searched for TimeWarp.Mediator Actions and Handlers
   /// </summary>
   /// <remarks>
   /// Will default to the calling assembly
diff --git a/Source/TimeWarp.State/Features/CloneState/Pipeline/StateTransactionBehavior.cs b/Source/TimeWarp.State/Features/CloneState/Pipeline/StateTransactionBehavior.cs
@@ -10,7 +10,7 @@ namespace TimeWarp.Features.StateTransactions;
 /// <remarks>
 ///   This behavior is part of the TimeWarp.State pipeline, intercepting actions (requests) to clone the relevant state before
 ///   proceeding. If an action fails, the system reverts to the cloned state, thus preventing partial state updates
-///   from corrupting the application state. It uses MediatR's pipeline behavior feature to hook into the request handling
+///   from corrupting the application state. It uses TimeWarp.Mediator's pipeline behavior feature to hook into the request handling
 ///   process.
 /// </remarks>
 /// <typeparam name="TRequest"></typeparam>
@@ -117,7 +117,7 @@ CancellationToken cancellationToken
 
       await Publisher.Publish(exceptionNotification, cancellationToken);
 
-      return default!;// It can be null, but we don't care since MediatR handles null values gracefully.
+      return default!;// It can be null, but we don't care since TimeWarp.Mediator handles null values gracefully.
     }
   }
 }
diff --git a/Source/TimeWarp.State/Features/ReduxDevTools/ReduxDevToolsOptions.cs b/Source/TimeWarp.State/Features/ReduxDevTools/ReduxDevToolsOptions.cs
@@ -17,7 +17,7 @@ public sealed class ReduxDevToolsOptions
     @"^(?:(?!\b" +
     @"System" +
     @"|Microsoft" +
-    @"|MediatR" +
+    @"|TimeWarp.Mediator" +
     @"|ReduxDevTools" +
     @"\b).)*$";
   // serialize is not implemented thus will use JSON.stringy
diff --git a/Tests/Client.Integration.Tests/Infrastructure/BaseTest.cs b/Tests/Client.Integration.Tests/Infrastructure/BaseTest.cs
@@ -22,7 +22,7 @@ protected BaseTest(ClientHost clientHost)
   private IServiceProvider ServiceProvider { get; }
 
   /// <summary>
-  /// Send a request to the MediatR pipeline
+  /// Send a request to the TimeWarp.Mediator pipeline
   /// </summary>
   /// <param name="request"></param>
   protected async Task Send(IRequest request) => await Sender.Send(request);
diff --git a/Tests/Test.App/Test.App.Client/Pipeline/MyBehavior.cs b/Tests/Test.App/Test.App.Client/Pipeline/MyBehavior.cs
@@ -5,7 +5,7 @@ namespace Test.App.Client.Pipeline;
 /// </summary>
 /// <typeparam name="TRequest"></typeparam>
 /// <typeparam name="TResponse"></typeparam>
-/// <remarks>see MediatR for more examples</remarks>
+/// <remarks>see TimeWarp.Mediator for more examples</remarks>
 public class MyBehavior<TRequest, TResponse> : IPipelineBehavior<TRequest, TResponse>
   where TRequest : notnull
 {
diff --git a/Tests/TimeWarp.State.Analyzer.Tests/TimeWarpStateActionAnalyser_Tests.cs b/Tests/TimeWarp.State.Analyzer.Tests/TimeWarpStateActionAnalyser_Tests.cs
@@ -26,8 +26,8 @@ public record SampleInvalidRecordAction : IAction { }
     const string TimeWarpStateAssemblyPath = @"TimeWarp.State.dll";
     analyzerTest.TestState.AdditionalReferences.Add(MetadataReference.CreateFromFile(TimeWarpStateAssemblyPath));
 
-    const string MediatRContractsAssemblyPath = @"TimeWarp.Mediator.Contracts.dll";
-    analyzerTest.TestState.AdditionalReferences.Add(MetadataReference.CreateFromFile(MediatRContractsAssemblyPath));
+    const string TimeWarpMediatorContractsAssemblyPath = @"TimeWarp.Mediator.Contracts.dll";
+    analyzerTest.TestState.AdditionalReferences.Add(MetadataReference.CreateFromFile(TimeWarpMediatorContractsAssemblyPath));
 
     await analyzerTest.RunAsync();
   }
@@ -55,8 +55,8 @@ public class SampleInvalidClassAction : IAction { }
     const string TimeWarpStateAssemblyPath = @"TimeWarp.State.dll";
     analyzerTest.TestState.AdditionalReferences.Add(MetadataReference.CreateFromFile(TimeWarpStateAssemblyPath));
 
-    const string MediatRContractsAssemblyPath = @"TimeWarp.Mediator.Contracts.dll";
-    analyzerTest.TestState.AdditionalReferences.Add(MetadataReference.CreateFromFile(MediatRContractsAssemblyPath));
+    const string TimeWarpMediatorContractsAssemblyPath = @"TimeWarp.Mediator.Contracts.dll";
+    analyzerTest.TestState.AdditionalReferences.Add(MetadataReference.CreateFromFile(TimeWarpMediatorContractsAssemblyPath));
 
     await analyzerTest.RunAsync();
   }
@@ -84,8 +84,8 @@ public struct SampleInvalidStructAction : IAction { }
     const string TimeWarpStateAssemblyPath = @"TimeWarp.State.dll";
     analyzerTest.TestState.AdditionalReferences.Add(MetadataReference.CreateFromFile(TimeWarpStateAssemblyPath));
 
-    const string MediatRContractsAssemblyPath = @"TimeWarp.Mediator.Contracts.dll";
-    analyzerTest.TestState.AdditionalReferences.Add(MetadataReference.CreateFromFile(MediatRContractsAssemblyPath));
+    const string TimeWarpMediatorContractsAssemblyPath = @"TimeWarp.Mediator.Contracts.dll";
+    analyzerTest.TestState.AdditionalReferences.Add(MetadataReference.CreateFromFile(TimeWarpMediatorContractsAssemblyPath));
 
     await analyzerTest.RunAsync();
   }
@@ -114,8 +114,8 @@ public class SampleInvalidDescendantClassAction : AbstractAction { }
     const string TimeWarpStateAssemblyPath = @"TimeWarp.State.dll";
     analyzerTest.TestState.AdditionalReferences.Add(MetadataReference.CreateFromFile(TimeWarpStateAssemblyPath));
 
-    const string MediatRContractsAssemblyPath = @"TimeWarp.Mediator.Contracts.dll";
-    analyzerTest.TestState.AdditionalReferences.Add(MetadataReference.CreateFromFile(MediatRContractsAssemblyPath));
+    const string TimeWarpMediatorContractsAssemblyPath = @"TimeWarp.Mediator.Contracts.dll";
+    analyzerTest.TestState.AdditionalReferences.Add(MetadataReference.CreateFromFile(TimeWarpMediatorContractsAssemblyPath));
 
     await analyzerTest.RunAsync();
   }
