Stratara.Validation 4.4.4

Prefix Reserved
There is a newer version of this package available.
See the version list below for details.
dotnet add package Stratara.Validation --version 4.4.4
                    
NuGet\Install-Package Stratara.Validation -Version 4.4.4
                    
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Stratara.Validation" Version="4.4.4" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="Stratara.Validation" Version="4.4.4" />
                    
Directory.Packages.props
<PackageReference Include="Stratara.Validation" />
                    
Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.
paket add Stratara.Validation --version 4.4.4
                    
#r "nuget: Stratara.Validation, 4.4.4"
                    
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
#:package Stratara.Validation@4.4.4
                    
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.
#addin nuget:?package=Stratara.Validation&version=4.4.4
                    
Install as a Cake Addin
#tool nuget:?package=Stratara.Validation&version=4.4.4
                    
Install as a Cake Tool

Stratara.Validation

Derived. The behaviour described here is specified under openspec/specs/. Those specifications are the source; this page explains and illustrates them.

License: MIT.

Vendor-neutral request validation for Stratara's CQRS pipeline. A mediator pipeline behavior runs your IValidator<T> implementations before the handler and throws an aggregated StrataraValidationException when validation fails — no third-party validation dependency in the default path.

Quick start

// 1. Register the behavior (outermost) + discover validators.
builder.Services
    .AddStrataraValidation()
    .AddValidatorsFromAssemblyContaining<IAppMarker>();

// 2. Write a validator (the contracts live in Stratara.Abstractions.Validation).
public sealed class CreateOrderValidator : IValidator<CreateOrder>
{
    public ValueTask<ValidationResult> ValidateAsync(CreateOrder cmd, CancellationToken ct = default)
        => ValueTask.FromResult(string.IsNullOrWhiteSpace(cmd.CustomerId)
            ? new ValidationResult([new ValidationFailure(nameof(cmd.CustomerId), "Customer is required.")])
            : ValidationResult.Success);
}

// 3. Catch the failure in your global handler and map it to your error model.
catch (StrataraValidationException ex)
{
    // ex.Failures -> RFC-7807 ProblemDetails 400, your error codes, etc.
}

How it works

  • AddStrataraValidation() registers IPipelineBehavior for both request shapes (IRequest and IRequest<TResult>). Register it before other behaviors so validation runs outermost — before authorization, auditing, and the handler.
  • All validators for a request run; their failures are aggregated.
  • Severity policy: only ValidationSeverity.Error blocks (throws StrataraValidationException). Warning and Info failures pass through and are logged.

Contracts

The validation contracts (IValidator<T>, ValidationResult, ValidationFailure, ValidationSeverity, StrataraValidationException) live in Stratara.Abstractions (namespace Stratara.Abstractions.Validation) so consumers can implement validators and catch the exception without referencing this behavior package.

The contract shape is FluentValidation-compatible; an optional Stratara.Validation.FluentValidation adapter can be shipped to plug FluentValidation validators into the same pipeline.

Dependencies

  • Stratara.Abstractions
  • Stratara.Mediator
  • Stratara.Diagnostics
  • Microsoft.Extensions.DependencyInjection.Abstractions
  • Microsoft.Extensions.Logging.Abstractions
Product Compatible and additional computed target framework versions.
.NET net10.0 is compatible.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
4.4.5 105 10/14/2026
4.4.4 374 10/10/2026
4.4.3 104 10/10/2026
4.4.2 398 10/2/2026
4.4.1 414 9/29/2026
4.4.0 145 9/27/2026
4.3.1 127 9/25/2026
4.3.0 386 9/23/2026
4.2.0 146 9/18/2026
4.1.1 98 9/16/2026
4.1.0 102 9/16/2026
4.0.4 833 9/14/2026
4.0.3 109 9/3/2026
4.0.2 606 9/3/2026
4.0.1 349 9/2/2026
4.0.0 649 8/31/2026
4.0.0-preview.1 77 8/31/2026
3.4.0 155 8/28/2026
3.3.0 344 8/25/2026
3.2.3 120 8/22/2026
Loading failed

A one-fix release. On the Redis-backed replay state, a host could report a replay still active after it had ended
it, holding publication back for up to one refresh interval. Nothing else changes; no configuration or migration is
needed.

### Fixed

- **A host no longer reports a replay active after it ended the replay itself.** On the Redis-backed replay state, a
 refresh that had read the marking just before the host's own deactivation could compare its generation before the
 deactivation and write the field after it, leaving `IsReplayActive` true — and publication held back — until the
 next refresh (`ProjectionReplay:RefreshSeconds`, default 5). The comparison and the write are now one step with the
 transition. Present since 4.4.2.