Stratara.Validation
3.1.6
dotnet add package Stratara.Validation --version 3.1.6
NuGet\Install-Package Stratara.Validation -Version 3.1.6
<PackageReference Include="Stratara.Validation" Version="3.1.6" />
<PackageVersion Include="Stratara.Validation" Version="3.1.6" />
<PackageReference Include="Stratara.Validation" />
paket add Stratara.Validation --version 3.1.6
#r "nuget: Stratara.Validation, 3.1.6"
#:package Stratara.Validation@3.1.6
#addin nuget:?package=Stratara.Validation&version=3.1.6
#tool nuget:?package=Stratara.Validation&version=3.1.6
Stratara.Validation
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()registersIPipelineBehaviorfor both request shapes (IRequestandIRequest<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.Errorblocks (throwsStrataraValidationException).WarningandInfofailures 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.AbstractionsStratara.MediatorStratara.DiagnosticsMicrosoft.Extensions.DependencyInjection.AbstractionsMicrosoft.Extensions.Logging.Abstractions
| Product | Versions 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. |
-
net10.0
- JetBrains.Annotations (>= 2025.2.4)
- Microsoft.Extensions.DependencyInjection.Abstractions (>= 10.0.8)
- Microsoft.Extensions.Logging.Abstractions (>= 10.0.8)
- Stratara.Abstractions (>= 3.1.6)
- Stratara.Diagnostics (>= 3.1.6)
- Stratara.Mediator (>= 3.1.6)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
### Changed
- **License changed from FSL-1.1-MIT to the MIT License.** Stratara is now OSI-approved open
source — free for any use, including commercial, with no competition clause and no two-year
conversion delay. The previous Functional Source License (source-available, converting to MIT
two years after each release) has been replaced outright. Package metadata now declares the
SPDX expression `MIT` (`PackageLicenseExpression`), so nuget.org renders a standard clickable
MIT license label instead of an embedded custom-license file. The `LICENSE` file at the repo
root now contains the standard MIT text and is still bundled into every package. No code or API
changes accompany this — it is purely a licensing and metadata change. Previously published
versions (3.0.20 through 3.1.5) remain under the FSL terms they shipped with; this change applies
to all versions released from here on.