Stratara.Validation 4.4.8

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


                    

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


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


                    

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


                            Install as a Cake Addin
                        

                    

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


                            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 143 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 110 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 store reader that catches up a large backlog and a singleton
work that runs long now answer their keep-alive, so neither leaves reminder errors in the silo's log. A silo that
joins while a singleton work runs long on another silo no longer fails its start. No API change, no schema change
and no migration.

### Fixed

- **A busy store reader or singleton work answers its keep-alive.** On the Orleans execution model, a projection or
 saga reader that caught up a backlog for longer than the runtime's response timeout made its keep-alive tick wait
 behind the catch-up, and Orleans logged `Could not deliver reminder tick` at Error, once per partition and
 keep-alive period. A singleton work whose run outlasted the timeout did the same. Nothing was lost, but a large
 catch-up left dozens of errors on the silo. The keep-alive and the poll now start a catch-up where none is
 running and do not wait for it. A partition is still read by one catch-up at a time, and a commit during a
 catch-up is still applied by it. A singleton work's keep-alive interleaves with its run, and runs still never
 overlap.
- **A silo starts while a singleton work runs long.** A silo that started while a singleton work it registers ran
 longer than the response timeout on another silo waited for that run in its own start. The start then failed
 with a `TimeoutException`. The call a starting silo makes to each singleton work and store reader now
 interleaves, so the start goes on.
- *Operate the Orleans execution model* says that a durable timer whose handler outlasts the response timeout
 still makes Orleans log `Could not deliver reminder tick` for that tick, and that the line says nothing about
 the timer. It also says that, outside a deploy, the line now points to an unreachable store reader or singleton
 work rather than a busy one.