Stratara.Validation 4.4.9

Prefix Reserved
.NET 10.0 This package targets .NET 10.0. The package is compatible with this framework or higher.
There is a newer version of this package available.
See the version list below for details. 
dotnet add package Stratara.Validation --version 4.4.9
                    


                    

                
NuGet\Install-Package Stratara.Validation -Version 4.4.9
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.9" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
<PackageVersion Include="Stratara.Validation" Version="4.4.9" />
                    


                            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.9
                    


                    

                
#r "nuget: Stratara.Validation, 4.4.9"
#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.9
#: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.9
                    


                            Install as a Cake Addin
                        

                    

                
#tool nuget:?package=Stratara.Validation&version=4.4.9
                    


                            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.8.0 144 11/6/2026
4.7.1 83 11/5/2026
4.7.0 536 10/30/2026
4.6.1 95 10/29/2026
4.6.0 192 10/28/2026
4.5.0 272 10/28/2026
4.4.10 203 10/26/2026
4.4.9 111 10/26/2026
4.4.8 252 10/24/2026
4.4.7 115 10/23/2026
4.4.6 221 10/22/2026
4.4.5 648 10/14/2026
4.4.4 395 10/10/2026
4.4.3 124 10/10/2026
4.4.2 470 10/2/2026
4.4.1 429 9/29/2026
4.4.0 152 9/27/2026
4.3.1 136 9/25/2026
4.3.0 400 9/23/2026
4.2.0 160 9/18/2026
Loading failed

A fix for hosts on the Orleans execution model. A host that removed or renamed a projection no longer has that
projection's store readers come back on every start and fail each entry; they retire once, as a saga's readers do. A
retired store reader now logs its retirement once instead of three times, and leaves no reminder error behind. No
API change, no schema change and no migration.

### Fixed

- **A reader of a removed projection retires.** On the Orleans execution model, a host that removed or renamed a
 projection kept the keep-alive reminders of its store readers. On every start of the silo they brought the readers
 back, and each one read the next entry of its partition, failed it because no projection of its name was
 registered, and tried again on the next tick, without end — a warning per partition and entry. Such a reader now
 retires the first time it is brought back, as a saga's reader already did: it unregisters its keep-alive, logs
 `117_136` `UnregisteredProjectionReaderRetired` (Information) once, reads nothing and deactivates. Its checkpoints
 stay, so a projection registered again resumes where it stopped; *Operate the Orleans execution model* says how to
 delete them. In a rolling deployment that adds a projection, a reader that lands on a silo of the earlier version
 refuses a rebuild's or a replay's pause, which then fails naming it, and a wait counts its partition as behind.
- **A retired store reader logs its retirement once.** A reader that retired as it was activated — of a partition
 beyond a lowered partition count, or of a saga the silo no longer registers — deactivated before it answered the
 call that activated it. Orleans forwarded that call to a new activation, which retired again, so the retirement was
 logged three times per reader and the keep-alive tick ended in `Could not deliver reminder tick` at Error. The
 reader now answers the call first and deactivates after it.