Stratara.Validation 3.1.5

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


                    

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


                            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 3.1.5
                    


                    

                
#r "nuget: Stratara.Validation, 3.1.5"
#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@3.1.5
#: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=3.1.5
                    


                            Install as a Cake Addin
                        

                    

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


                            Install as a Cake Tool

Stratara.Validation

License: FSL-1.1-MIT (Functional Source License — source-available; converts to MIT after 2 years). Not OSI-approved OSS.

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
3.1.7 61 7/1/2026
3.1.6 316 6/22/2026
3.1.5 102 6/22/2026
3.1.4 889 6/15/2026
3.1.3 105 6/10/2026
3.1.2 113 6/5/2026
3.1.1 845 6/1/2026
3.1.0 103 5/30/2026

### Added

- **Configurable snapshot strategy** (`Stratara.Abstractions`, `Stratara.Infrastructure`) — the
 snapshot cadence is no longer hard-coded. A new `Stratara.Abstractions.EventSourcing.ISnapshotStrategy`
 decides, per stream, whether the event-sourcing runtime should write a snapshot:
 `bool ShouldSnapshot(Type aggregateType, long currentVersion, long lastSnapshotVersion)`.
 `AddEventSourcing()` registers the default `VersionThresholdSnapshotStrategy` (snapshot every 50
 versions — identical to the previous behaviour) via `TryAddSingleton`, so existing consumers see no
 change. To take over the policy, register your own singleton `ISnapshotStrategy` (it overrides the
 default whether registered before or after `AddEventSourcing()`): vary the threshold per aggregate
 type, construct `new VersionThresholdSnapshotStrategy(threshold)` for a different uniform cadence, or
 register `NoSnapshotStrategy` to disable snapshotting entirely. This replaces the previously
 hard-coded `UseSnapshots`/`SnapshotRange` constants in the default snapshot service, which were not
 actually configurable despite the documentation implying they were.
- **`AddDomainEventTypesFromAssemblyContaining<T>()`** (`Stratara.Abstractions`) — registers *only* the
 domain event types consumed by an assembly's aggregate `Apply(TEvent)` methods in the trusted-type
 resolver, without registering the aggregate types themselves and without pulling any projection / saga
 / command-handler classes into DI. Use it in a host that only needs to deserialize event payloads off
 the message bus or event stream — typically a dedicated projection or saga worker — but must not wire
 the handler classes (and their runtime dependencies) that `AddProjectionsFromAssemblyContaining<T>`
 would register. Complements the existing `AddAggregatesFromAssemblyContaining<T>` (which additionally
 registers the aggregate types) and `AddTrustedType<T>` (single type).