Mediator Releases

6.6.0 TBD

BREAKING Enhancement

ISerializerService interface removed. Mediator now consumes Shiny.ISerializer from the new Shiny.Extensions.Serialization package (registered automatically by AddShinyMediator). Replace any direct ISerializerService injection with Shiny.ISerializer. The runtime-typed Deserialize(string, Type) overload moved to the Shiny.Mediator.Infrastructure.SerializerRuntimeExtensions extension class.

BREAKING Enhancement

SysTextJsonSerializerService class removed. No replacement — the default ISerializer is Shiny.Json.Default, which is wired into DI by AddShinyMediator. Tests that need ad-hoc / anonymous-type serialization can construct a Shiny.Impl.DefaultJsonSerializer and add DefaultJsonTypeInfoResolver to its chain.

BREAKING Enhancement

ShinyMediatorBuilder.SetSerializer<T>() removed. Customize serialization by registering a different Shiny.ISerializer in DI before AddShinyMediator, or by calling Shiny.Json.AddContext / Shiny.Json.AddResolver to extend the shared chain.

BREAKING Enhancement

HttpHandlerServices.Serializer type changed from ISerializerService to Shiny.ISerializer. Affects subclasses and direct constructions of the record.

BREAKING Enhancement

AOT-strict JSON is now the default. Mediator no longer falls back to reflection-based STJ. Without a registered JsonSerializerContext, any request/response/event/scheduled-command that hits the serializer throws InvalidOperationException: No JsonTypeInfo registered for type 'T'. Register your types via [ShinyJsonContext] partial class AppContext : JsonSerializerContext with [JsonSerializable(typeof(T))] entries — module-init auto-registers it with Shiny.Json. See the new JSON Serialization section.

Feature

Mediator now auto-generates JSON wiring for every registered handler’s contract types. A new source-generator step walks every [MediatorSingleton] / [MediatorScoped]-discovered handler, transitively collects request, response, command, event, stream-request element types plus their public property types (so RideTime → Position and the like get pulled in automatically), emits a per-type JsonConverter<T> for each in-assembly contract type, and ships a single __ShinyMediatorContractsJsonResolver per assembly that wires them via JsonMetadataServices.CreateValueInfo plus collection wrappers (List<T> / T[] / IEnumerable<T> / IList<T> / ICollection<T> / IReadOnlyList<T> / IReadOnlyCollection<T> / IAsyncEnumerable<T>). A [ModuleInitializer] registers the resolver with Shiny.Json before Main. Default on — opt out with <ShinyMediatorGenerateJsonContext>false</ShinyMediatorGenerateJsonContext>. Eliminates the manual [ShinyJsonContext] / [JsonSerializable] declaration for the common handler-flow path; cross-assembly types (e.g. types from third-party NuGets) still need explicit registration.

Feature

OpenAPI HTTP clients are now AOT-clean end-to-end. When GenerateJsonConverters="true" on a MediatorHttp item, the generator emits a custom IJsonTypeInfoResolver per client that wires every generated model, contract, and enum (including Nullable<TEnum> and List<T> / T[] shapes) via JsonMetadataServices factories, plus a [ModuleInitializer] that registers it with Shiny.Json. Zero consumer setup required.

Feature

StorageCacheService refactored to a non-generic envelope. InternalCacheEntry<T> → InternalCacheEntry carrying a pre-serialized string ValueJson. The persisted shape no longer depends on the closed-generic type of the cached value, eliminating the failure mode where caching IReadOnlyList<ParkRideInfo> threw No JsonTypeInfo registered for type 'InternalCacheEntry<IReadOnlyList<ParkRideInfo>>' under the strict chain. StorageCacheService now takes Shiny.ISerializer alongside its existing dependencies.

Feature

Built-in AppSupport JSON resolver auto-registers infrastructure wire types. A new Shiny.Mediator.Infrastructure.AppSupportJsonResolver (in Shiny.Mediator.AppSupport) wires JsonTypeInfo for InternalCacheEntry, OfflineStore, CacheItemConfig, and the AbstractFileStorageService (category → key → filename) index via hand-rolled converters. A [ModuleInitializer] registers it with Shiny.Json — users never have to declare these envelope types in their own JsonSerializerContext.

Feature

Built-in AspNet JSON resolver auto-registers ValidateResult. A new Shiny.Mediator.Infrastructure.AspNetJsonResolver (in Shiny.Mediator.AspNet) wires JsonTypeInfo for ValidateResult. ValidationJsonExceptionHandler no longer calls raw JsonSerializer.Serialize (which silently bypassed the chain and was AOT-hostile) — it now routes through the injected Shiny.ISerializer so the 400-response body works under the strict chain without users declaring ValidateResult anywhere.

Feature

AI tool generator no longer reflects through SerializeToElement. Generated AIFunction.InvokeCoreAsync previously called JsonSerializer.SerializeToElement(arguments) (reflection-based, AOT-hostile) to extract typed values from the MEAI AIFunctionArguments dictionary. It now reads each property directly via a switch covering the three runtime shapes — already-typed boxed primitive, JsonElement, or null — with explicit numeric widening (e.g. long → int) for STJ’s number defaults. Complex / collection property types deserialize through Shiny.Json.Default.Options so the chain (which the new contracts resolver populates) supplies the JsonTypeInfo.

Feature

MemoryCacheService no longer uses reflection over MemoryCache internals. Remove(partialMatch: true) and Clear now use an in-process key index kept in sync via PostEvictionCallback, making the cache AOT/trim-safe and changing prefix removal from O(all entries) to O(matches).

Enhancement

New JsonConverterSourceGenerator.GenerateJsonConverter(context, typeSymbol, attachAttribute: false) overload. Emits just the per-type JsonConverter<T> class without trying to wire a [JsonConverter] attribute via a partial declaration — so the contracts resolver can generate converters for non-partial user records without forcing partial everywhere. The legacy [SourceGenerateJsonConverter] path keeps attachAttribute: true semantics unchanged.

Fix

MemoryCacheExtensions.RemoveByKeyStartsWith actually filters by prefix. Previous implementation was missing the StartsWith predicate and silently removed every entry in the cache.

Enhancement

Bumped Shiny.Extensions.DependencyInjection to v5 and added Shiny.Extensions.Serialization v5.

6.5.0 TBD

Feature

New TickerQ library to enable command scheduling

Enhancement

Aligning DI internals with Shiny.Extensions.DependencyInjection

Fix

Generated JSON converters now handle nullable enum properties under NativeAOT — when MediatorHttp items use GenerateJsonConverters="true", the JsonConverterSourceGenerator previously detected only TypeKind.Enum and missed Nullable<TEnum> (which has TypeKind.Struct). Nullable enum properties fell through to JsonSerializer.Deserialize<TEnum?> and JsonSerializer.Serialize. At runtime under NativeAOT this triggers NullableConverter<TEnum>, which uses reflection to look up the inner enum’s converter and throws “missing native code or metadata” against the nullable converter type. The generator now unwraps Nullable<TEnum> and emits (TEnum?)Enum.Parse<TEnum>(reader.GetString()!) on read and value.Prop?.ToString() on write — fully inline and trim/AOT-safe

6.4.0 - May 17, 2026

Fix

Fixed MAUI StorageService.DeleteFile — inverted condition (!File.Exists) prevented cached files from ever being deleted

Fix

Fixed service scope leak in LocalEventExecutor — each event handler was creating a new scope instead of reusing the parent scope, leading to accumulated unreleased scopes

Fix

Fixed child scope disposal in MediatorContext — Request, Send, and Publish now properly dispose child scopes in a finally block

Fix

Fixed StorageCacheService concurrency — replaced the single global semaphore with per-key locking via the new KeyedLocker, so the factory runs exactly once per key without serializing unrelated keys. Get now also takes the per-key lock, eliminating a sliding-expiration race where two concurrent reads could overwrite each other

Fix

Fixed MemoryCacheService.GetOrCreate cache stampede — IMemoryCache.GetOrCreateAsync does not lock the factory, so N concurrent callers for the same key would each invoke the factory. Now wraps the factory in a per-key KeyedLocker so it runs exactly once per key

Fix

Fixed HttpRequestCacheMiddleware double-wrap bug — TryCacheEntry was wrapping the result in a CacheEntry<TResult> before calling ICacheService.Set<TResult>(...), which itself wraps the value, so the cache stored CacheEntry<CacheEntry<TResult>> and subsequent Get<TResult> calls always missed

Fix

Fixed HttpRequestCacheMiddleware cache stampede — Get → next → Set was unsynchronized, so concurrent requests for the same URL would all hit the network. Now per-key locked via KeyedLocker

Enhancement

New Shiny.Mediator.Infrastructure.KeyedLocker — per-key async mutual exclusion primitive used by cache services and middleware for stampede protection; safe for any singleton component that needs to serialize work by key

Fix

Fixed PublishToBackground exception handling — TryHandle was fire-and-forget (_ =), so exception handlers were never awaited. Now properly awaited

Fix

Fixed InMemoryCommandScheduler scope and activity lifecycle — moved scope/activity creation outside the try block and added finally disposal to prevent leaks

Fix

Fixed Blazor InternetService.WaitForAvailable — single TaskCompletionSource meant only one concurrent caller could wait. Now supports multiple concurrent waiters

Fix

Fixed MemoryCacheService.Remove with partial match — was modifying the cache entry collection during enumeration, causing InvalidOperationException. Now snapshots matching keys before removal

Fix

Fixed QueuedEventMiddleware SampleState timer — added CancellationTokenSource to properly cancel in-flight timers on dispose and prevent stale callbacks

Fix

Fixed AbstractFileStorageService concurrent access — simplified semaphore patterns and prevented potential deadlocks from double semaphore acquisition in GetFileIndexer. Data-file writes are now serialized per (category, key) with KeyedLocker, so two concurrent Set calls on the same key can no longer tear the file content

Fix

Removed dead copy-pasted code from EventStream extension method (unused TaskCompletionSource and cancellation registration)

6.3.0 - April 2026

Feature

AI Tool Integration — expose your mediator contracts as AI-callable tools via Microsoft.Extensions.AI. Annotate contracts with [Description] and the source generator produces AIFunction wrappers with JSON schemas automatically. Enable with ShinyMediatorGenerateAITools MSBuild property.

Enhancement

AI source generator is now built into the main Shiny.Mediator.SourceGenerators — no separate Shiny.Mediator.MicrosoftAI.SourceGenerators package needed

Enhancement

Compiler error SHINYMED100 is emitted when ShinyMediatorGenerateAITools is enabled but Microsoft.Extensions.AI is not referenced

Enhancement

[Sample] and [Throttle] event middleware is now registered automatically as part of the default middleware — no need to call a separate registration method

Fix

Fixed async enumerator disposal in stream middleware (ReplayStreamMiddleware, SentryStreamRequestMiddleware, TimerRefreshStreamRequestMiddleware) — enumerators are now properly disposed in a finally block to prevent resource leaks

Fix

Fixed thread-safety in MAUI MauiEventCollector — page tracking collection is now synchronized with a lock to prevent concurrent modification issues

Fix

Fixed service scope disposal in Mediator.Request — scope is now properly disposed after request completion

Fix

Fixed PublishToBackground scope lifetime — service scope and activity were being disposed before the background task completed, now properly managed within the background task

Fix

Fixed InMemoryCommandScheduler race condition — timer creation is now inside the lock to prevent duplicate timers

Fix

Fixed MAUI ConnectivityBroadcaster and MauiEventCollector to resolve IApplication from the service provider instead of constructor injection to avoid circular dependency issues

6.2.1 - February 26, 2026

Feature

New [Sample] attribute for event handler methods - fixed-window sampling where the first event starts a timer, subsequent events replace the pending delegate without resetting the timer, and the last event is executed when the window expires

Fix

[Throttle] now implements true throttle behavior - the first event executes immediately, then all subsequent events within the cooldown window are discarded. Previously, [Throttle] implemented debounce/sample behavior

// Sample: fixed-window, last event wins at end of window
// No explicit registration needed — included in default middleware

public partial class MyEventHandler : IEventHandler<MyEvent>
{
  [Sample(1000)] // 1 second window
  public Task Handle(MyEvent myEvent, IMediatorContext context, CancellationToken ct)
  {
    // First event starts a 1s timer. Subsequent events replace the pending delegate
    // but do NOT reset the timer. When the timer fires, the last event is executed.
  }
}

// Throttle: first event executes immediately, cooldown discards the rest
// No explicit registration needed — included in default middleware

public partial class MyEventHandler : IEventHandler<MyEvent>
{
  [Throttle(1000)] // 1 second cooldown
  public Task Handle(MyEvent myEvent, IMediatorContext context, CancellationToken ct)
  {
    // First event executes immediately. All events within the next 1s are discarded.
    // After cooldown expires, the next event executes immediately again.
  }
}

6.2.0 - February 19, 2026

Feature

New Throttle attribute for event handler methods - ensures last event is delivered after X seconds

Enhancement

Middleware can be ordered in terms of execution by marking your middleware class with [MiddlewareOrder(int)] (higher numbers are closer to the handler)

services.AddShinyMediator(x => x.AddThrottledEventHandlers());

public class MyEventHandler : IEventHandler<MyEvent>
{
  [Throttle(1000)] // respresents milliseconds, so 1000 = 1 second
  public Task Handle(MyEvent myEvent, EventContext context)
  {
    // this will ensure that if multiple MyEvent are published within 5 seconds, only the last one will be delivered after the 5 seconds is up
    // if only one event is published, it will be delivered immediately
    // if multiple events are published, the timer resets with each new event and only the last event is delivered after 5 seconds of no new events
  }
}

v6.1.3 - February 7, 2026

Fix

OpenAPI handler generation no longer uses C# required so that json converter generation is not broken

v6.1.2 - February 6, 2026

Enhancement

New HTTP Response Cache Middleware - Caches HTTP responses based on CacheControl MaxAge

Fix

OpenAPI handler generation naming would get URI parameters in the name

v6.1.1 - January 16, 2026

Fix

OpenAPI source generator was not generating URI path correctly for PUT/POST

v6.1.0 - TBD

Fix

New extension IMediator.EventStream could drop events and has been redesigned for speed

Fix

RuntimeEventRegister is now thread-safe

Enhancement

BaseHttpRequestHandler now handles commands

v6.0.2 - January 3, 2026

Fix

ASPNET endpoint source generator was missing a namespace when used in a library that didn’t use the web sdk (missing global using)

v6.0.1 - December 21, 2025

Fix

Fix OpenAPI improper/duplicate type generation

BREAKING Fix

OpenAPI source generator automatically adds a postfix of HttpRequest if contract postfix is left empty

Fix

Fix OpenAPI nullables

Fix

Fix OpenAPI timespans

v6.0.0 - December 5, 2025

BREAKING Feature

Moving to .NET 8 & 10 as minimum target

BREAKING Feature

New HTTP Client Source Generation now generates handlers, contracts, JSON converters, and registration to make it fully compatible. This will require you to call a new registration method, but its setup through MediatorHttpItem remains the same

BREAKING Feature

DirectHttpRequest is gone. You can create your own HTTP objects as before which will source generate a handler

Enhancement

New PublishToBackground on IMediator and IMediatorContext intended to fix scoping issues that can occur on aspnet fire & forget scenarios. This new method spawns a new child scope so you can continue to run without worrying about disposal. Note that you can still use Publish to await all event completions using the same service scope

Enhancement

The HTTP Client source generation no longer ignores missing OperationIDs. It inferes the contact name using the HTTP verb and path info (ie. GET /user/list = GetUserList)

Enhancement

ASPNET no longer enforces operation ID in the attribute setup

Enhancement

We now support async enumerable responses. Sample below:

Enhancement

[GitHub #51] by codelisk

PrismRegionNavigationCommand for region-based navigation

Async Enumerable Responses

// if your endpoint does NOT support server sent events, you can still use IAsyncEnumerable<T> - just remove the IServerSentEventsStream interface
[Get("/api/sse")]
public class ServerSentEventsRequest : IStreamRequest<EventItem>, IServerSentEventsStream
{
}

v5

v5.1 - October 27, 2025

BREAKING Chore

ASPNET source generator no longer generates a registration ASPNET method. Register your handlers manually or with [MediatorScopedAttribute]

Enhancement

ASPNET now generates endpoints for stream requests

Enhancement

New utility extensions for IMediator WaitForEvent and EventStream that listens on event publisher

Feature

NEW mediator extension in aspnet that allows you to send stream requests as server sent events - you need to create your own endpoint at this, but you can call mediator.RequestServerSentEvents(MyStreamRequest, IHttpContextAccessor) and mediator.EventStreamToServerSentEvents<TEventType>(IHttpContextAccessor)

v5.0 - October 25, 2025

Feature

New contract key generator - sample below

Feature

HTTP generated contracts can now generate JSON converters to remove any need of reflection. This feature is off by default

Feature

Re-releasing standalone Sentry library due to AOT not being supported on MAUI via Sentry.Diagnostics

Feature

New source generator to register middleware without having to worry about open generic registration

Feature

Mediator source generator now generates an AOT/Trimmable request & stream request executor along with dependency injection registration

BREAKING Feature

Cache, Timer Refresh, Replay, and other mediator attributes now source generate against handlers. The breaking change is that your handler must now be partial. This update helps remove all of the reflection required to use the method level attributes.

BREAKING Feature

Handlers & Middleware registration methods are no longer generated by our source generators. We now generate a module initializer that automatically sets all registrations up in a global registry. To use the global registry, simply call services.AddShinyMediator(x => x.AddRegistry()). We will not call this method automatically, to ensure users are aware of how/where the magic is happening

BREAKING Enhancement

MAUI storage services like offline now use the cache directory

Enhancement

New RuntimeEventRegistration service that you can add event handlers to at runtime dynamically

Enhancement

HTTP handlers now use the HTTP Client Factory internally

Fix

Child context should not receive a copy of the parent’s headers as this will crash things like caching for a child request

Chore

RegisterHandlerAttribute is called MediatorSingletonAttribute or MediatorScopedAttribute - These new attributes also handle middleware registration

BREAKING Chore

IRequestKey has been renamed to IContractKey

New JSON Converter Source Generator

This feature allows you to generate JSON converters at compile time instead of using reflection at runtime. This is especially useful for AOT scenarios like iOS and Blazor WebAssembly. Unfortunately, we are unable to “piggyback” source generators (ours to System.Text.Json), so we found the easiest way to do this was to generate JSON converters, NOT the types emitted by the System.Text.Json source generator.

Setting JSON converters allow you to push JsonConverterAttribute on the type instead of having to pass around a centralized JSON context.

We have two flavours of JSON generation. The first one (and most importantly) is for our HTTP client code generation. NOTE that JsonConverter generation is NOT enabled by default yet.

<ItemGroup>
  <MediatorHttp Include="OpenApiRemote"
                Uri="https://youruri"
                GenerateJsonConverters="true"
                Visible="false" />
</ItemGroup>

Secondly, there will be times for features such as offline data storage or caching where data needs to serialize down to disk. These types obviously aren’t generated by our source generators and are likely types you’ve created. We’ve created a secondary way to create JSON converters for your own types.

[SourceGenerateJsonConverter]
public partial class YourClass
{
  public string? Name { get; set; }
  public int Age { get; set; }
}

NOTE: Your class must be partial and the attribute must be placed on the type directly.

New Contract Key Source Generator

This feature allows you to generate a contract key at compile time instead of using reflection at runtime. This is especially useful for AOT scenarios like iOS and Blazor WebAssembly.

• Type must be partial
• Keys support property names with formatting (like DateTime)
• If no key is specified, it will generate a key format for all public instance properties that are not null

[Shiny.Mediator.ContractKeyAttribute("MyClass_{MyProperty}_{Date:yyyyMMdd}")]
public partial class MyClass
{
  public string? MyProperty { get; set;}
  public string? UnusedProperty { get; set;}
  public DateTime? Date { get; set;}
}

// UnusedProperty will not be included in the contract key
// If a property is null, it is replaced with an empty string
// Date will be formatted as yyyyMMdd if not null

JSON Converter Generation

<ItemGroup>
  <MediatorHttp Include="OpenApiRemote"
                Uri="https://youruri"
                GenerateJsonConverters="true"
                Visible="false" />
</ItemGroup>

v4

4.9.1

Fix

[GitHub #40]

Fix storage service deadlock

Fix

Fix another release semaphore state in storage service indexing

4.9.0 - July 26, 2025

Feature

Blazor now has a connectivity event broadcaster. Simply add <InternetConnectivity /> to your main layout (don’t add more than 1)

Enhancement

IContractKeyProvider provides a new injectable and external way of providing contract keys allowing you to pull values from configuration, source generation, etc without using reflection. Our current provider works on reflection to maintain backwards compat, but we have a lot of things planned here

Enhancement

Blazor now has a IConnectivityEventHandler that you can implement to receive connectivity events

Enhancement

UseBlazor will no longer error on .NET MAUI apps. It will only register the Blazor event collector. If running in the browser, all of Blazor’s infrastructure is registered

Enhancement

HTTP requests and responses are put on the IMediatorContext.Headers so you can access them in your handlers

Fix

Blazor connectivity handler was not broadcasting changes

Fix

[GitHub #39]

Only release semaphore slim call, if that call passed the wait state

4.8.0 - July 18, 2025

Enhancement

User notification exception handler will no longer try to react for subrequests

Enhancement

IMediatorContext.Exception is now set if an exception is thrown in the scope of a send/request

Enhancement

HTTP requests now ensure base URL + route name doesn’t produce double slashes based on how you configure either side

Enhancement

Improved logging and diagnostics for error handling

Enhancement

Improved logging in UserErrorNotifications exception handler

Feature

Blazor now contains a InternetConnectivity component that you can add to your pages. It will broadcast to the IConnectivityEventHandler while alive. If you set NoInternetMessage, it will also render the text to your page. Text has no styling. Wrap this component however you want

4.7.0 - June 25, 2025

BREAKING Enhancement

HTTP decorators now take the cancellation token for the handler request

Enhancement

HTTP decorators now allows you to generate the models only (and not generating the contracts for the HTTP calls themselves) - Sample Below

Enhancement

HTTP request generator now allows you to specify if you want the classes accessor to be public or internal. Sample below

Enhancement

Cancellation tokens now traverse all of the store types like cache, offline, and storage services

Fix

Blazor will now clear cache when called

<ItemGroup>
    <MediatorHttp Include="Json File or Name"
                  Uri="If using name above"
                  Namespace="YourNamespace"
                  ContractPostfix="Request"
                  UseInternalClasses="true"
                  GeneratorModelsOnly="true"
                  Visible="false"/>
</ItemGroup>

4.6.3 - 4.6.6 - June 20, 2025

Fix

HTTP Request source generator was emitting duplicate generated code attributes

Fix

HTTP Request Handler wi[InlineData(”./Http/standard.json”, “HttpRequest”, “TestApi”, false)]ll properly use injected serializer from Mediator

Fix

UseOpenApi has been removed from ASPNET attributes - use ExcludeFromDescription

4.6.2 - June 18, 2025

Fix

HTTP Request source generator was not emitting inline enum values properly

4.6.1 - June 17, 2025

Fix

ASPNET endpoint source generator was duplicating endpoints in partial classes

Chore

Remove unnecessary Uno library from Shiny.Mediator.Uno

4.6.0 - June 16, 2025

BREAKING Enhancement

Moving to FluentValidation v12

Chore

Bump SharpYaml and Microsoft OpenAPI

4.5.0 - June 10, 2025

BREAKING Enhancement

ASP.NET source generator now generates minimal API routes and the dependency injection mapping

BREAKING Enhancement

ASP.NET source generator now places http attributes on the handler method, not the class

Enhancement

ASP.NET source generator allows you to place optional MediatorHttpGroupAttribute that allows you to work against multiple handler methods within a class

4.4.0 - June 3, 2025

Enhancement

NEW MAUI Event collector now watches application events to collect MAUI pages. This allows for better management of nested pages and events

Enhancement

ConnectivityBroadcaster now uses a technique similar to new MAUI event collector to find event handlers

Fix

HTTP source generator will now use double instead of int when number format is not set

Enhancement

Improvements to how diagnostic activities are created and managed through the pipeline - Sentry is now deprecated because of this. Use Sentry.DiagnosticSource to hook into standard diagnostics

BREAKING Enhancement

Handler registration in source generator will now use ShinyMediatorBuilder so it can be used inside of Add

BREAKING Enhancement

HTTP timeout is now set via configuration and has been removed from attribute

BREAKING Enhancement

HTTP request decorators are no longer generic based - you can access the raw object off the mediator context

BREAKING Enhancement

Performance logging is no longer installed with default middleware since activity diagnostics are builtin

Feature

Direct/Raw HTTP request with builtin handler

4.2.2 - May 23, 2025

Enhancement

Source generator target name now uses a more specific name to not conflict with other libraries

Enhancement

Bump Uno to v6

4.2.1 - May 8, 2025

Fix

Exception handlers were meant to be optional - Mediator will now properly manage exception handler optionally and ensure they aren’t pinned in scope which causes an error for Microsoft Extensions DI

4.2.0 - April 25, 2025

Feature

[GitHub #25] by codelisk

Prism Region Event Collector

Enhancement

[GitHub #27] by JeremyBP

MAUI Event collector will iterate the page modal stack

Enhancement

ASPNET extension now offers a ValidationJsonExceptionHandler which takes a middleware exception and translates it back to the client

Enhancement

Sentry extension will no longer attempt to do transactions if Sentry is not active in dependency injection (due to debug mode or code flags of some sort)

Fix

[GitHub #30]

MSFT memorycache extension was not committing Set values properly (only seen during force cache refresh)

Fix

[GitHub #28] by codelisk

Fix timer refresh stream middleware when no header is present in mediator context

Fix

Timer refresh stream middleware using proper timespan value and ensuring cancellation on timer

Fix

Timer refresh stream middleware will now fire the initial request immediately instead of imposing a wait

Fix

Command scheduling when header is not present in command scheduling

BREAKING Chore

Command scheduler does not need to validate due date - middleware already handles it

Enhancement

Timer refresh now has lots of debug logging to help users detect issues

4.1.0 - March 28, 2025

Fix

Cache configuration values not checked properly in middleware

BREAKING Enhancement

ICacheControl has been removed as it polluted the contract model AND could reset cache values used by other calls to that cached value

Enhancement

IMediatorContext.ForceCacheRefresh and SetCacheConfig are now proper extension methods off IMediatorContext

Enhancement

ICacheService.Set now returns the CacheEntry

Fix

ForceCacheRefresh now returns cache information

4.0.4 - March 24, 2025

Fix

[GitHub #22] by codelisk

Caching middleware not returning value

Fix

Fixed Microsoft Extensions MemoryCache extension method ‘GetEntries’ to work on NET9

4.0.3 - March 23, 2025

Fix

CachingRequestMiddleware throws NullReferenceException

>

Fix

Ensure cache expiration or hit on StorageCacheService

Enhancement

HTTP handling now uses proper logging templates

Enhancement

Adding Mediator:Http:Debug = true to your configuration allows mediator HTTP request to log out all of the HTTP request & responses

4.0.2 - March 14, 2025

Fix

If deserialization in file store fails for any reason, return default

Fix

Remove unnecessary library from Dapper extension

Fix

Proper generic constraint added to RequestMiddleware

Fix

InMemoryCommandScheduler now bypasses middleware and exception handling

Chore

Move to SLNX

Chore

Move to centralized nuget packages

4.0.1 - March 5, 2025

Enhancement

IHttpRequestDecorator now takes in an IMediatorContext argument

4.0.0 - March 4, 2025

Feature

ICommandExecuter, IEventExecutor, IStreamRequestExecutor, and IRequestExecutor all added behind mediator to allow more plug points for things like Sentry to watch scope

BREAKING Enhancement

IMediator.Request now returns a tuple with context and result instead of having a separate extension

BREAKING Enhancement

RequestContext, EventContext, CommandContext, and EventAggregatedContext are now all MediatorContext. (I)MediatorContext has ChildContexts to replace EventAggregatedContext

BREAKING Enhancement

BypassMiddleware & BypassExceptionHandling is now built directly into the mediator context

BREAKING Enhancement

You no longer pass headers to mediator calls, there is a callback that provides an IMediatorContext where you can setup all the necessary headers directly

Enhancement

MediatorContext now has an activity source for providing telemetry through handlers and middleware

Enhancement

MAUI connectivity broadcaster now watches for pages (and their binding context) appearing to see if it should receive connectivity event as well as sending last event value immediately

Fix

Stream Requests now have their service scope properly disposed even if an error occurs during enumeration

BREAKING Chore

MediatorContext Values is now called Headers

BREAKING Chore

ShinyConfigurator is now called ShinyMediatorBuilder

Enhancement

Ability to skip source generation using

<PropertyGroup>
  <ShinyMediatorSkipGenerate>true</ShinyMediatorSkipGenerate>
</PropertyGroup>

v3

3.3.1 - February 20, 2025

Feature

Uno Platform Integration

Feature

Sentry Integration

Enhancement

Ability to bypass middleware using headers - mediator.Send(…, cancelToken, Headers.BypassMiddleware)

Enhancement

Ability to bypass error traps using Headers.BypassExceptionHandling - all Shiny Mediator middleware that error trap will respect this header

Enhancement

Performance middleware uses the better, allocation free version of the Stopwatch

BREAKING Fix

Offline and persistent cache could collide if the same type used both

Fix

[GitHub #16] by ss-lordjay

HTTP post bodies do not serialize property

Chore

Remove Sourcelink as it is built in now

3.2.0 - January 30, 2025

Feature

Global Exception Handling via new IExceptionHandler

Enhancement

User error notification now works on global exception handling

MAUI

Feature

ConnectivityBroadcaster allows your services to take IEventHandler<ConnectivityChanged> to have your services listen to one central location of connectivity change events

3.1.2 - January 28, 2025

Fix

Event handlers were not getting their sent headers set in the event context

Fix

Removed cancellation token from event context to prevent misuse

Fix

RequestContext property RequestHandler has been renamed to Handler to be consistent with other context objects

Fix

Ensure only one cache service can be installed

App Support

Enhancement

Internet service now has an event to monitor connectivity

MAUI

Enhancement

Support Multi-Window MAUI apps in event collector

Enhancement

AlertDialogService now looks at Windows like event collector

Fix

MauiHttpRequestDecorator safeties geolocation header appending and improves configuration

Prism

Enhancement

Add PrismNavigationCommand & PrismNavigationRecord bases to inherit

3.1.0 - January 25, 2025

Core

Enhancement

Ability to control timer refresh through header arguments

Enhancement

You can now force cache refreshing through Request(contract, cancel token, CacheExtensions.ForceCacheRefreshHeader)

Enhancement

Ability to set cache arguments through header arguments

Enhancement

Commands can now be scheduled through headers

Dapper Extension

Enhancement

Dapper requests now have requests keys built-in to their request objects

Enhancement

Dapper requests now accept transactions and command types

3.0.0 - January 24, 2025

Feature

New Dapper Extension that allows you to easily (and smartly) use Dapper with InterpolatedSql in a smart way that allows you to take advantage of all the mediator middleware. This further allows you to make the middleware act as a SQL interceptor as well.

BREAKING Feature

Commands replace Requests and also have their own pipeline

Feature

Command Scheduling with basic in-memory scheduler

Feature

Ability to send headers to a mediator command/request/stream that is added to the context

Enhancement

ReplayStreamMiddleware now sets values on the context as it passes each layer

BREAKING Enhancement

AddShinyMediator now has a flag to allow you to remove all of the default middleware (defaults to true)

Enhancement

Timeout support for HTTP handler

Enhancement

Full logging in HTTP handler to debug your requests

Enhancement

Replay middleware will not try to return handler result when timeout detection (removes downstream crash)

Enhancement

Caching setup is now in the base Shiny.Mediator allowing for easier caching extension

Enhancement

Shiny.Mediator.AppSupport has a ‘Persistent Cache’ that survives app restarts - Works great for offline scenarios too

Enhancement

Replay will now optional grab cache if available first and ONLY then will it fall back to online

Enhancement

ASP.NET extensions now include MapMediatorPost extension methods of the IEndpointRouteBuilder to work well with minimal APIs

BREAKING Enhancement

EventContext is passed to event handlers as well as middleware

BREAKING Enhancement

Command and Request contexts are now available at the handlers

BREAKING Enhancement

Stream request handlers now bring in request contexts

Fix

Offline middleware returns offline result when TimeoutException is thrown by internal middleware or handler

Chore

Shiny.Mediator.Caching is deprecated and replaced by Shiny.Mediator.Caching.MicrosoftMemoryCache

BREAKING Chore

ExecutionContext has been renamed to RequestContext

BREAKING Chore

EventExecutionContext is now called EventContext

v2

2.1.1 - Oct 30, 2024

Enhancement

More Prism navigation contract control

2.1.0 - Oct 19, 2024

Enhancement

Reducing some infrastructure reflection as we work towards a potential AOT compliant library

Enhancement

Downgrading source generator libraries to work with older net8 SDKs

Enhancement

OpenAPI generator now factors in TimeSpans

Enhancement

Serializer service now exists in the main library with optional configuration

Enhancement

IMediator Publish now allows you to setup publish in parallel or sequential

Fix

HttpRequestHandler will use serializer service

2.0.3 - Oct 7, 2024

Enhancement

Easy extensions methods for AddShinyMediator for the MauiAppBuilder and WebAssemblyHostBuilder

2.0.2 - Oct 6, 2024

Fix

ASPNET extension was not generating the proper result type for POST & PUT

2.0.1 - Oct 6, 2024

Fix

OpenApiGenerator was not returning subtypes from string

Enhancement

ASPNET OperationId is not enforced through the attribute constructor

Chore

Improved source generator logging

2.0.0 - Oct 4, 2024

Feature

Most middleware and internal handlers now support configuration via Microsoft.Extensions.Configuration vs using attributes - HTTP, Timer Refresh, Offline, Stream Replay, Performance Logging, Caching, User Notifications

Feature

Blazor now supports offline, stream replay, and user notification middleware

Feature

ExecutionContext allows you to add metadata from middleware that can be consumed by the caller (IMediator.RequestWithContext return ExecutionResult, Send now returns ExecutionContext)

Feature

EventAggregatedExecutionContext(List of EventExecutionContext) allows you to add metadata from middleware that can be consumed by the caller - IMediator.Publish now returns this by default

Enhancement

OpenApiGenerator now allows DateOnly, TimeOnly, and Stream results

Enhancement

OpenApiGenerator offers better support for inline enums and subtypes (node based APIs)

Enhancement

Improved logging, so you can see your pipeline execution pipeline front to back

Enhancement

Request Handlers that return a result that is marked with IEvent will now publish it automatically

Enhancement

Stream Replay will now also wait for internet connectivity before pumping a new data request

Fix

OpenApiGenerator now tacks on global namespace to all object types

Fix

Registration source generator did not default the library namespace

Fix

[GitHub #11] by osyyyS

Shell and NRE fixes for MAUI Event Collector

Fix

OpenApiGenerator returns INT by default when no format is supplied

BREAKING Chore

IRequestMiddleware and IStreamRequestMiddleware signature changed to support ExecutionContext and reduce argument count

BREAKING Chore

Contract feature attributes have been removed for ReplayStream, Cache, Resilience, & Offline

BREAKING Chore

ReplayStream and Offline are only across sessions now

BREAKING Chore

TimedLoggingRequestMiddleware has been renamed to PerformanceLoggingMiddleware (including registration extensions)

BREAKING Chore

TimedLoggingAttribute has been removed in favour of ONLY using configuration going forward

BREAKING Chore

UserNotifyAttribute has been removed in favour of ONLY using configuration going forward

v1

1.8.1 - September 14, 2024

Fix

OpenApiGenerator was not writing return results if they were arrays

1.8.0 - September 11, 2024

Feature

New HTTP Request Handler and framework

Feature

New HTTP Request OpenAPI source generator

Enhancement

ICacheControl is now available for contracts that allows more direct control over your cached calls

Fix

OfflineAvailableAttribute was not allowed to be applied to contracts

1.7.4 - August 9, 2024

Fix

Fix implicit namespace usage

1.7.3 - August 7, 2024

Fix

Source generators were not generating scoped handlers

Enhancement

aspnet HttpGet and HttpDelete is now supported. Contracts are mapped using [AsParamters]

1.7.2 - July 28, 2024

Enhancement

IRequestKey now has default interface implement to use ReflectKey

Enhancement

Minor timestampedresult signature improvement

1.7.1 - July 28, 2024

Enhancement

Attributes for offline, caches, etc can now be applied on the request contract AND/OR the request handlers

Enhancement

IRequestKey.ReflectKey looks through all public, instance, getters that are not null into part of the key

Enhancement

Logging is now built into the core mediator library

Enhancement

Request pipeline now has logging built-in

Enhancement

ExceptionHandlerEventMiddleware & TimedLoggingRequestMiddleware moved from MAUI to main library

1.7.0 - July 20, 2024

Feature

New contract validation middleware using data annotations or fluentvalidation

Enhancement

Add new contract TimestampedResult generic to help with timestamps of when a cache or offline bundle is from

1.6.0 - July 7, 2024

Enhancement

Refresh timer middleware is now installed by default

Enhancement

Add Name to HTTP attribute in ASP.NET extension

Enhancement

Streaming AsyncEnumerables now mapped by ASP.NET extension

More MemoryCache extensions (clear by partial key, get entries)

1.5.0 - July 5, 2024

Feature

Shiny.Mediator.AspNet - that allows you to map your request handlers directly to HTTP endpoints

BREAKING Enhancement

Source Generator attributes have been renamed from RegisterHandler & RegisterMiddleware to SingletonHandler/ScopedHandler & SingletonMiddleware/ScopedMiddleware

1.4.5 - July 3, 2024

Feature

Strongly typed navigation now exists for Shell, just like Prism. This functionality is built into Shiny.Mediator.Maui

1.4.0 - June 30, 2024

Feature

Shiny.Mediator.Prism - this new package allows you to easily create strongly typed navigation routes & arguments while working across modules

1.3.0 - June 29, 2024

Enhancement

Request Keys can be controlled by implementing IRequestKey on your request object allowing you to return a cache/offline/replay key based on your arg values

Enhancement

MainThread middleware can now be used on request handlers as well

Enhancement

UserExceptionRequestMiddleware is now configurable and can be appled with attribute [UserExceptionRequestMiddleware] on each request handler method

Feature

Mediator middleware that has some form of store (cache/replay/offline) now responds to a global event called Shiny.Mediator.Middleware.FlushAllStoresEvent in Shiny.Mediator that calls all stores to be flushed

Feature

Resiliency middleware (Shiny.Mediator.Resilience} based on Microsoft.Extensions.Resilience

Feature

Offline Availability Middleware separated from caching and allows you to store across app sessions as needed (part of Shiny.Mediator.Maui)

BREAKING Feature

Caching middleware is now Shiny.Mediator.Caching and uses IMemoryCache under the hood

1.2.0 - June 19, 2024

Feature

Streaming Requests that request IAsyncEnumerable

Feature

Streaming Request Middleware

Feature

OOTB Streaming Request Middleware - Timer Refresh & Replay

1.1.0 - June 17, 2024

Fix

Void requests IRequestHandler<T> would not always resolve

Fix

Relaxed generic constraints on RequestMiddleware

Enhancement

MAUI CacheRequestMiddleware can hnow have cache flushed per item or all

1.0.0 - June 15, 2024

Our initial release - checkout the following:

• Getting Started
• Blog Post