Stratara.Validation 3.1.2

There is a newer version of this package available.
See the version list below for details.
dotnet add package Stratara.Validation --version 3.1.2
                    
NuGet\Install-Package Stratara.Validation -Version 3.1.2
                    
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.2" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="Stratara.Validation" Version="3.1.2" />
                    
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.2
                    
#r "nuget: Stratara.Validation, 3.1.2"
                    
#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.2
                    
#: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.2
                    
Install as a Cake Addin
#tool nuget:?package=Stratara.Validation&version=3.1.2
                    
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.6 96 6/22/2026
3.1.5 65 6/22/2026
3.1.4 316 6/15/2026
3.1.3 100 6/10/2026
3.1.2 110 6/5/2026
3.1.1 841 6/1/2026
3.1.0 99 5/30/2026

### Added

- **New package `Stratara.Testing`** — test doubles and assertion helpers so consumers can
 unit-test Stratara-based code without Postgres or RabbitMQ testcontainers. Reference it from
 test projects only.
 - `AggregateTestHarness<T>` + `Aggregate.Rehydrate<T>(...)` — given/when/then rehydration of an
   aggregate from events using the same reflection-based `Apply(...)` dispatch as the production
   aggregation service. It throws on an event with no matching `Apply` overload so a forgotten or
   mistyped overload fails the test; opt back into the production-lenient skip with
   `IgnoringUnmappedEvents()`.
 - `InMemoryKeyStore` — an `IKeyStore` that mints random 256-bit DEKs per `KeyScope` and supports
   rotation / revocation / scope-erasure without a master KEK or key file.
 - `TestBlobEncryptor.CreateAesGcm()` — the real AES-GCM `ISecureBlobEncryptor` over an
   `InMemoryKeyStore`, so blob round-trips exercise production encryption.
 - `InMemoryMessageBus` — an `IMessageBus` with synchronous in-process dispatch and a `Published`
   list for assertions.
 - `TestSessionContext` / `TestSessionContextProvider` — preset Actor/Subject `SessionContext`
   values and an `ISessionContextProvider` double.
 - `TestTenants.Of("acme")` — stable, deterministic tenant/user ids from readable slugs.
   `TestSessionContext` sets both correlation and causation ids so the context can drive
   event-store writes.
 - `TestEvent.Create(payload, ...)` — wrap an event payload in `IEvent<T>` with realistic
   metadata; `ProjectionTester.HandleAsync(projection, event)` — invoke a projection's private
   `HandleAsync` handler directly to unit-test it against mocked repositories.
- **New package `Stratara.Testing.EntityFrameworkCore`** — spins up the **real** event-sourcing
 write stack (`IEventSource`, `IAggregationService`, snapshots, the EF Core write store) against a
 shared in-memory SQLite database in one call, so tests exercise production code paths without
 Postgres or Docker. Reference it from test projects only.
 - `EventStoreTestHost.Create(...)` — owns the SQLite connection + service provider; exposes
   `ExecuteAsync(IEventSource)`, `AggregateAsync<T>(streamId)`, the preset `Session`, and the
   recording `Outbox`.
 - `AddStrataraTestingEventStore<TWriteDbContext>(connection, tenantId)` — the lower-level DI
   extension; `StrataraTestWriteDbContext` — a ready-made concrete write context;
   `RecordingEventBundleOutboxDispatcher` — captures emitted bundles for assertions.
 - The lockstep family grows from 22 to 24 packable packages.