One Rule, Many Surfaces: Validation as a Design Concern
A first look at Jeninnet.Validation 1.0.0-preview.1
Release at a glance: 1.0.0-preview.1 · .NET 11 (STS) · C# 15 · 25 packages · 997 tests · MIT
NuGet ·
Documentation ·
Release notes
One rule, one engine, many surfaces. The same declaration feeds the API, the UI, the schema, the
client, and the tests.
Open a typical .NET solution and count where the same validation rule appears. There is a [Required]
on the model. A FluentValidation rule in the application layer. A required array in the OpenAPI
document. A conditional branch in the Blazor form. A JSON Schema consumed by the browser. A test that
repeats the boundary values one more time.
None of these copies is obviously wrong. Each one is locally reasonable. Together they form a
maintenance contract with no owner.
The problem is not that .NET lacks validation libraries.…