com.wallstop-studios.dxmessaging 2.1.0 → 2.1.2

package/.github/workflows/dotnet-tests.yml

@@ -0,0 +1,72 @@
+name: dotnet-tests
+
+on:
+  push:
+    branches:
+      - master
+      - main
+      - develop
+  pull_request:
+    branches:
+      - "*"
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Setup .NET
+        uses: actions/setup-dotnet@v3
+        with:
+          dotnet-version: "9.0.x"
+
+      - name: Install reportgenerator tool
+        run: |
+          dotnet tool install --global dotnet-reportgenerator-globaltool
+          echo "$HOME/.dotnet/tools" >> "$GITHUB_PATH"
+
+      - name: Restore
+        run: dotnet restore SourceGenerators/WallstopStudios.DxMessaging.SourceGenerators.Tests/WallstopStudios.DxMessaging.SourceGenerators.Tests.csproj
+
+      - name: Run generator diagnostics tests
+        run: >
+          dotnet test SourceGenerators/WallstopStudios.DxMessaging.SourceGenerators.Tests/WallstopStudios.DxMessaging.SourceGenerators.Tests.csproj
+          --configuration Release
+          --collect:"XPlat Code Coverage"
+
+      - name: Generate coverage summary
+        run: |
+          mkdir -p artifacts/coverage
+          reportgenerator \
+            -reports:".artifacts/SourceGenerators.Tests/TestResults/**/coverage.cobertura.xml" \
+            -targetdir:"artifacts/coverage" \
+            -reporttypes:"TextSummary;HtmlSummary;Cobertura"
+          cat artifacts/coverage/Summary.txt
+
+      - name: Upload coverage report
+        uses: actions/upload-artifact@v4
+        with:
+          name: generator-coverage
+          path: artifacts/coverage
+
+      - name: Check for TODO/FIXME markers
+        shell: bash
+        run: |
+          set -uo pipefail
+          if rg --files-with-matches "(TODO|FIXME)" \
+                --hidden \
+                --no-ignore \
+                -g '!.git/**' \
+                -g '!.artifacts/**' \
+                -g '!node_modules/**' \
+                -g '!Tests/**/TestResults/**' \
+                -g '!PLAN.md' \
+                -g '!.vs/**'; then
+            echo "::error::Found TODO/FIXME markers in the repository. Please resolve or suppress them."
+            exit 1
+          else
+            echo "No TODO/FIXME markers detected."
+          fi

package/.lychee.toml

@@ -17,10 +17,12 @@ accept = ["200..=299", 429]
 # Only check web links
 scheme = ["https", "http"]
 
-# Ignore common local/test URLs
+# Ignore endpoints that block automated clients (local hosts, CF challenges)
 exclude = [
   "^https?://localhost",
   "^http://127\\.0\\.0\\.1",
   "^https?://0\\.0\\.0\\.0",
-  "^file://"
+  "^file://",
+  # NPM package page serves a Cloudflare JS challenge to non-browser clients; registry endpoint remains covered.
+  "^https://www\\.npmjs\\.com/package/com\\.wallstop-studios\\.dxmessaging$"
 ]

package/AGENTS.md

@@ -24,6 +24,7 @@
 - Do not use underscores in function names, especially test function names.
 - Do not use regions, anywhere, ever.
 - Avoid `var` wherever possible, use expressive types.
+- Do not use nullable reference types.
 
 ## Testing Guidelines
 

package/Docs/Comparisons.md

@@ -34,10 +34,10 @@ These sections are auto-updated by the PlayMode comparison benchmarks in `Tests/
 
 | Message Tech                       | Operations / Second | Allocations? |
 | ---------------------------------- | ------------------- | ------------ |
-| DxMessaging (Untargeted) - No-Copy | 14,902,000          | No           |
-| UniRx MessageBroker                | 18,026,000          | No           |
-| MessagePipe (Global)               | 96,978,000          | No           |
-| Zenject SignalBus                  | 2,520,000           | Yes          |
+| DxMessaging (Untargeted) - No-Copy | 14,734,000          | No           |
+| UniRx MessageBroker                | 18,044,000          | No           |
+| MessagePipe (Global)               | 97,774,000          | No           |
+| Zenject SignalBus                  | 2,600,000           | Yes          |
 
 ### Comparisons (macOS)
 

package/Docs/EmitShorthands.md

@@ -70,10 +70,10 @@ public sealed class ScoreReporter
 }
 
 [DxUntargetedMessage]
-public readonly struct ScoreChanged
+[DxAutoConstructor]
+public readonly partial struct ScoreChanged
 {
     public readonly int Value;
-    public ScoreChanged(int value) => Value = value;
 }
 ```
 

package/Docs/Helpers.md

@@ -186,34 +186,32 @@ public readonly partial struct ComplexMessage
 
 ## Why Use Attributes Instead of Manual Implementation
 
-### ❌ Manual Way (Verbose, Error-Prone)
+### ✅ Attribute Definition (Clean, Automatic)
 
 ```csharp
-public readonly struct Heal : ITargetedMessage<Heal>
+[DxTargetedMessage]
+[DxAutoConstructor]
+public readonly partial struct Heal
 {
     public readonly int amount;
-
-    // You write this yourself (boring!)
-    public Heal(int amount)
-    {
-        this.amount = amount;
-    }
-
-    // Required plumbing (easy to mess up!)
-    public Type MessageType => typeof(Heal);
 }
 ```
 
-### ✅ Attribute Way (Clean, Automatic)
+### What the generator emits (for reference)
 
 ```csharp
-[DxTargetedMessage]
-[DxAutoConstructor]
-public readonly partial struct Heal
+// Auto-generated by DxMessaging (no need to hand-write this)
+public readonly partial struct Heal : ITargetedMessage<Heal>
 {
     public readonly int amount;
+
+    public Heal(int amount)
+    {
+        this.amount = amount;
+    }
+
+    public Type MessageType => typeof(Heal);
 }
-// Constructor and plumbing generated automatically!
 ```
 
 #### Benefits
@@ -223,14 +221,28 @@ public readonly partial struct Heal
 - ✅ **Cleaner** - Focus on data, not boilerplate
 - ✅ **Refactor-safe** - Add field? Constructor updates automatically!
 
-## Complete Example: Before & After
+## Complete Example: Attribute Definition vs Generated Output
 
-### Before (Manual - 20 lines)
+### Attribute Definition (8 lines)
 
 ```csharp
-using DxMessaging.Core.Messages;
+using DxMessaging.Core.Attributes;
 
-public readonly struct PlayerDamaged : IBroadcastMessage<PlayerDamaged>
+[DxBroadcastMessage]
+[DxAutoConstructor]
+public readonly partial struct PlayerDamaged
+{
+    public readonly int amount;
+    public readonly string damageType;
+    public readonly GameObject source;
+}
+```
+
+### Generated Output (20 lines you never write)
+
+```csharp
+// Auto-generated by DxMessaging (for reference only)
+public readonly partial struct PlayerDamaged : IBroadcastMessage<PlayerDamaged>
 {
     public readonly int amount;
     public readonly string damageType;
@@ -247,65 +259,76 @@ public readonly struct PlayerDamaged : IBroadcastMessage<PlayerDamaged>
 }
 ```
 
-### After (Attributes - 9 lines!)
+### Result
 
-```csharp
-using DxMessaging.Core.Attributes;
+- ✅ Same functionality
+- ✅ Less code to maintain
+- ✅ Automatically updates when you add/remove fields
+- ✅ Works for class messages too
+- ✅ Zero effort once you mark the struct partial
 
-[DxBroadcastMessage]
+## Advanced: Manual Implementation (When Attributes Aren't Enough)
+
+Attributes cover almost every scenario. If you intentionally drop `[DxTargetedMessage]`, `[DxUntargetedMessage]`, or `[DxBroadcastMessage]`, you'll need to hand-write the interface implementations and constructors shown in the “generated output” examples. Keep the attributes unless you have a very specific data-backed reason not to.
+
+### Generic Message Interfaces (Zero-Boxing for Structs)
+
+`readonly struct` messages marked with the attributes already implement the generic interfaces, so emissions stay allocation-free. You get the same performance characteristics as the manual approach without writing any plumbing.
+
+```csharp
+[DxTargetedMessage]
 [DxAutoConstructor]
-public readonly partial struct PlayerDamaged
+public readonly partial struct Heal
 {
     public readonly int amount;
-    public readonly string damageType;
-    public readonly GameObject source;
 }
 ```
 
-**Result:** Same functionality, 55% less code, zero boilerplate!
+### "Do I HAVE to use attributes?"
 
-## Advanced: Manual Implementation (When Attributes Aren't Enough)
+Technically no—but without them you must write the constructor, interface implementation, and `MessageType` property yourself (for speed, you can optionally leave this off, but it might box on certain call paths). Leaving the attributes on keeps everything consistent for the whole team.
 
-Sometimes you might want full control and skip source generators. You can implement interfaces manually:
+```csharp
+[DxUntargetedMessage]
+[DxAutoConstructor]
+public readonly partial struct MyMsg { }
+```
 
-### Generic Message Interfaces (Zero-Boxing for Structs)
+### "What if I want custom constructor logic?"
 
-**For performance-critical code**, implement the generic interfaces directly:
+Keep the attributes and add a factory/helper so you still benefit from the generated constructor:
 
 ```csharp
-using DxMessaging.Core.Messages;
-
-public readonly struct Heal : ITargetedMessage<Heal>
+[DxUntargetedMessage]
+[DxAutoConstructor]
+public readonly partial struct ComplexMessage
 {
-    public readonly int amount;
+    public readonly int value;
 
-    public Heal(int amount)
+    public static ComplexMessage FromRaw(int rawValue)
     {
-        this.amount = amount;
+        int clamped = Math.Clamp(rawValue, 0, 100);
+        return new ComplexMessage(clamped);
     }
-
-    // Required for IMessage
-    public Type MessageType => typeof(Heal);
 }
 ```
 
-#### Why use generics?
+If you truly must write a custom constructor, drop `[DxAutoConstructor]` for that type but keep the `[DxUntargetedMessage]`/`[DxTargetedMessage]` attribute so the interface plumbing stays consistent.
 
-- Avoids boxing structs (important for performance)
-- Provides stable `MessageType` without `GetType()` calls
-- Same performance as attribute-based approach
+### "Can I mix attribute-based and manual messages?"
 
-##### When to use
+Yes. Attribute-driven messages happily coexist with string messages and any manual implementations you already have. You can migrate gradually by converting one message at a time:
 
-- Hot path messages (sent/received every frame)
-- Very large structs where boxing matters
-- When you want explicit control
-
-###### When to use attributes
+```csharp
+[DxUntargetedMessage]
+[DxAutoConstructor]
+public readonly partial struct MessageA
+{
+    public readonly int value;
+}
 
-- 99% of cases (they generate the same code!)
-- Cleaner, less boilerplate
-- Easier to maintain
+// Existing manual message types keep working alongside attribute-driven ones.
+```
 
 ## Extension Methods (Emit Helpers)
 
@@ -549,50 +572,42 @@ public readonly partial struct MyMessage : IUntargetedMessage<MyMessage>
 
 ### "What if I want custom constructor logic?"
 
-Use manual implementation:
+Keep the attributes and wrap the generated constructor with a helper so you can inject custom logic without losing the source-generated plumbing:
 
 ```csharp
-public readonly struct ComplexMessage : IUntargetedMessage<ComplexMessage>
+[DxUntargetedMessage]
+[DxAutoConstructor]
+public readonly partial struct ComplexMessage
 {
     public readonly int value;
 
-    public ComplexMessage(int rawValue)
+    public static ComplexMessage FromRaw(int rawValue)
     {
-        // Custom logic
-        value = Math.Clamp(rawValue, 0, 100);
+        int clamped = Math.Clamp(rawValue, 0, 100);
+        return new ComplexMessage(clamped);
     }
-
-    public Type MessageType => typeof(ComplexMessage);
 }
 ```
 
+If you truly need to hand-craft the constructor, drop `[DxAutoConstructor]` for that specific type but keep the `[DxUntargetedMessage]`/`[DxTargetedMessage]` attribute so the interface implementation is still generated.
+
 ### "Do attributes affect runtime performance?"
 
 **No!** Source generation happens at **compile time**. Generated code is identical to hand-written code. Zero runtime overhead.
 
 ### "Can I mix attributes and manual implementation?"
 
-**Not on the same type**, but you can have:
-
-- Some messages using attributes
-- Other messages using manual implementation
-- Mix and match across your codebase
+Yes. Attribute-driven messages happily coexist with any legacy manual messages or string messages you already emit. Convert types gradually—one message at a time:
 
 ```csharp
-// Message A: Attributes
 [DxUntargetedMessage]
 [DxAutoConstructor]
-public readonly partial struct MessageA { public readonly int value; }
-
-// Message B: Manual
-public readonly struct MessageB : IUntargetedMessage<MessageB>
+public readonly partial struct MessageA
 {
     public readonly int value;
-    public MessageB(int value) { this.value = value; }
-    public Type MessageType => typeof(MessageB);
 }
 
-// Both work perfectly together!
+// Existing manual messages keep working alongside attribute-driven ones.
 ```
 
 ## Troubleshooting Source Generators
@@ -609,7 +624,7 @@ public readonly struct MessageB : IUntargetedMessage<MessageB>
 ##### Fix
 
 ```csharp
-// ❌ Missing partial
+// ❌ Missing partial, will not compile
 [DxAutoConstructor]
 public readonly struct MyMsg { }
 

package/Docs/Install.md

@@ -9,7 +9,8 @@ This page helps you install DxMessaging into a Unity 2021.3+ project using the U
 - Unity Package Manager > Add package from git URL...
 - Paste:
 
-```text
+```bash
+# Unity UPM: Add package from git URL...
 https://github.com/wallstop/DxMessaging.git
 ```
 

package/Docs/Patterns.md

@@ -874,7 +874,7 @@ public class GameEvent : ScriptableObject
 
 // DxMessaging message (modern, type-safe)
 [DxUntargetedMessage]
-public readonly struct SceneTransitionRequested { }
+public readonly partial struct SceneTransitionRequested { }
 
 // Bridge: SOA Event → DxMessaging
 public class SOAEventBridge : MonoBehaviour

package/Docs/Performance.md

@@ -12,17 +12,19 @@ See also: `Docs/DesignAndArchitecture.md#performance-optimizations` for design d
 
 ## Windows
 
-| Message Tech                       | Operations / Second | Allocations? |
-| ---------------------------------- | ------------------- | ------------ |
-| Unity                              | 2,490,000           | Yes          |
-| DxMessaging (GameObject) - Normal  | 8,520,000           | No           |
-| DxMessaging (Component) - Normal   | 8,542,000           | No           |
-| DxMessaging (GameObject) - No-Copy | 9,426,000           | No           |
-| DxMessaging (Component) - No-Copy  | 9,552,000           | No           |
-| DxMessaging (Untargeted) - No-Copy | 14,900,000          | No           |
-| Reflexive (One Argument)           | 2,832,000           | No           |
-| Reflexive (Two Arguments)          | 2,348,000           | No           |
-| Reflexive (Three Arguments)        | 2,364,000           | No           |
+| Message Tech                               | Operations / Second | Allocations? |
+| ------------------------------------------ | ------------------- | ------------ |
+| Unity                                      | 2,564,000           | Yes          |
+| DxMessaging (GameObject) - Normal          | 8,476,000           | No           |
+| DxMessaging (Component) - Normal           | 8,474,000           | No           |
+| DxMessaging (GameObject) - No-Copy         | 9,418,000           | No           |
+| DxMessaging (Component) - No-Copy          | 9,536,000           | No           |
+| DxMessaging (Untargeted) - No-Copy         | 14,736,000          | No           |
+| DxMessaging (Untargeted) - Interceptors    | 6,618,000           | No           |
+| DxMessaging (Untargeted) - Post-Processors | 5,244,000           | No           |
+| Reflexive (One Argument)                   | 2,828,000           | No           |
+| Reflexive (Two Arguments)                  | 2,360,000           | No           |
+| Reflexive (Three Arguments)                | 2,358,000           | No           |
 
 ## macOS
 

package/Docs/QuickStart.md

@@ -60,8 +60,7 @@ public readonly partial struct TookDamage
     public readonly int amount;
 }
 
-// Performance option: generic interfaces on structs (zero boxing)
-// public readonly struct Heal : ITargetedMessage<Heal> { public readonly int amount; public Heal(int amount) { this.amount = amount; } }
+// Performance option: keep [DxTargetedMessage] on a readonly struct to stay zero-boxing friendly, and drop [DxAutoConstructor] only if you need custom constructor logic.
 
 // Optional parameters with custom defaults
 [DxTargetedMessage]

package/Editor/Analyzers/Microsoft.CodeAnalysis.CSharp.dll.meta

@@ -11,15 +11,26 @@ PluginImporter:
   isExplicitlyReferenced: 0
   validateReferences: 1
   platformData:
+  - first:
+      : Any
+    second:
+      enabled: 0
+      settings:
+        Exclude Editor: 0
+        Exclude Linux64: 1
+        Exclude OSXUniversal: 1
+        Exclude WebGL: 1
+        Exclude Win: 1
+        Exclude Win64: 1
   - first:
       Any: 
     second:
-      enabled: 1
+      enabled: 0
       settings: {}
   - first:
       Editor: Editor
     second:
-      enabled: 0
+      enabled: 1
       settings:
         DefaultValueInitialized: true
   - first:

package/Editor/Analyzers/Microsoft.CodeAnalysis.dll.meta

@@ -11,6 +11,17 @@ PluginImporter:
   isExplicitlyReferenced: 0
   validateReferences: 1
   platformData:
+  - first:
+      : Any
+    second:
+      enabled: 0
+      settings:
+        Exclude Editor: 0
+        Exclude Linux64: 1
+        Exclude OSXUniversal: 1
+        Exclude WebGL: 1
+        Exclude Win: 1
+        Exclude Win64: 1
   - first:
       Any: 
     second:

package/Editor/Analyzers/System.Collections.Immutable.dll.meta

@@ -11,6 +11,17 @@ PluginImporter:
   isExplicitlyReferenced: 0
   validateReferences: 1
   platformData:
+  - first:
+      : Any
+    second:
+      enabled: 0
+      settings:
+        Exclude Editor: 0
+        Exclude Linux64: 1
+        Exclude OSXUniversal: 1
+        Exclude WebGL: 1
+        Exclude Win: 1
+        Exclude Win64: 1
   - first:
       Any: 
     second:

package/Editor/Analyzers/System.Reflection.Metadata.dll.meta

@@ -11,15 +11,26 @@ PluginImporter:
   isExplicitlyReferenced: 0
   validateReferences: 1
   platformData:
+  - first:
+      : Any
+    second:
+      enabled: 0
+      settings:
+        Exclude Editor: 0
+        Exclude Linux64: 1
+        Exclude OSXUniversal: 1
+        Exclude WebGL: 1
+        Exclude Win: 1
+        Exclude Win64: 1
   - first:
       Any: 
     second:
-      enabled: 1
+      enabled: 0
       settings: {}
   - first:
       Editor: Editor
     second:
-      enabled: 0
+      enabled: 1
       settings:
         DefaultValueInitialized: true
   - first:

package/Editor/Analyzers/System.Runtime.CompilerServices.Unsafe.dll.meta

@@ -11,6 +11,17 @@ PluginImporter:
   isExplicitlyReferenced: 0
   validateReferences: 1
   platformData:
+  - first:
+      : Any
+    second:
+      enabled: 0
+      settings:
+        Exclude Editor: 0
+        Exclude Linux64: 1
+        Exclude OSXUniversal: 1
+        Exclude WebGL: 1
+        Exclude Win: 1
+        Exclude Win64: 1
   - first:
       Any: 
     second:

package/Editor/Analyzers/WallstopStudios.DxMessaging.SourceGenerators.dll.meta

@@ -18,9 +18,10 @@ PluginImporter:
     second:
       enabled: 0
       settings:
-        Exclude Editor: 1
+        Exclude Editor: 0
         Exclude Linux64: 1
         Exclude OSXUniversal: 1
+        Exclude WebGL: 1
         Exclude Win: 1
         Exclude Win64: 1
   - first:
@@ -31,7 +32,7 @@ PluginImporter:
   - first:
       Editor: Editor
     second:
-      enabled: 0
+      enabled: 1
       settings:
         CPU: AnyCPU
         DefaultValueInitialized: true

package/Editor/AssemblyInfo.cs

@@ -0,0 +1,3 @@
+using System.Runtime.CompilerServices;
+
+[assembly: InternalsVisibleTo("WallstopStudios.DxMessaging.Tests.Editor")]

package/Editor/AssemblyInfo.cs.meta

@@ -0,0 +1,3 @@
+fileFormatVersion: 2
+guid: 55bb3ae7ef064633b5fe4b17ce29f8cc
+timeCreated: 1761880591

package/Editor/CustomEditors/MessagingComponentEditor.cs

@@ -7,6 +7,7 @@ namespace DxMessaging.Editor.CustomEditors
     using Core.Diagnostics;
     using Core.MessageBus;
     using Core.Messages;
+    using DxMessaging.Editor.Testing;
     using Unity;
     using UnityEditor;
     using UnityEngine;
@@ -66,6 +67,26 @@ namespace DxMessaging.Editor.CustomEditors
                 return;
             }
 
+            MessagingComponentInspectorState inspectorState =
+                MessagingComponentEditorHarness.Capture(component);
+            ProviderDiagnosticsView providerDiagnostics = inspectorState.ProviderDiagnostics;
+
+            if (providerDiagnostics.SerializedProviderMissingWarning)
+            {
+                EditorGUILayout.HelpBox(
+                    "Auto-configure serialized provider is enabled, but no provider asset is assigned.",
+                    MessageType.Warning
+                );
+            }
+
+            if (providerDiagnostics.SerializedProviderNullBusWarning)
+            {
+                EditorGUILayout.HelpBox(
+                    "The serialized provider resolved without returning a message bus. Verify the provider implementation.",
+                    MessageType.Warning
+                );
+            }
+
             if (component._registeredListeners.Count == 0)
             {
                 EditorGUILayout.LabelField("No listeners registered.");