micro-elements - MicroElements.AspNetCore.OpenApi.FluentValidation 7.2.3
Applies FluentValidation rules to OpenAPI schemas generated by Microsoft.AspNetCore.OpenApi (IOpenApiSchemaTransformer).
PM> Install-Package MicroElements.AspNetCore.OpenApi.FluentValidation -Version 7.2.3 -Source https://www.myget.org/F/micro-elements/api/v3/index.json
> nuget.exe install MicroElements.AspNetCore.OpenApi.FluentValidation -Version 7.2.3 -Source https://www.myget.org/F/micro-elements/api/v3/index.json
> dotnet add package MicroElements.AspNetCore.OpenApi.FluentValidation --version 7.2.3 --source https://www.myget.org/F/micro-elements/api/v3/index.json
<PackageReference Include="MicroElements.AspNetCore.OpenApi.FluentValidation" Version="7.2.3" />
Copy to clipboard
source https://www.myget.org/F/micro-elements/api/v3/index.json
nuget MicroElements.AspNetCore.OpenApi.FluentValidation ~> 7.2.3
Copy to clipboard
> choco install MicroElements.AspNetCore.OpenApi.FluentValidation --version 7.2.3 --source https://www.myget.org/F/micro-elements/api/v2
Import-Module PowerShellGet
Register-PSRepository -Name "micro-elements" -SourceLocation "https://www.myget.org/F/micro-elements/api/v2"
Install-Module -Name "MicroElements.AspNetCore.OpenApi.FluentValidation" -RequiredVersion "7.2.3" -Repository "micro-elements"
Copy to clipboard
MicroElements.Swashbuckle.FluentValidation
Use FluentValidation rules instead of ComponentModel attributes to define swagger schema.
Note: For WebApi see: https://github.com/micro-elements/MicroElements.Swashbuckle.FluentValidation.WebApi
Statuses
Supporting the project
MicroElements.Swashbuckle.FluentValidation is developed and supported by @petriashev for free in his spare time. If you find MicroElements.Swashbuckle.FluentValidation useful, please consider financially supporting the project via OpenCollective which will help keep the project going 🙏.
Usage
1. Minimal API
MinimalApi.csproj
<Project Sdk="Microsoft.NET.Sdk.Web">
<PropertyGroup>
<TargetFramework>net8.0</TargetFramework>
<Nullable>enable</Nullable>
<ImplicitUsings>enable</ImplicitUsings>
</PropertyGroup>
<ItemGroup>
<PackageReference Include="FluentValidation.AspNetCore" Version="11.3.1" />
<PackageReference Include="MicroElements.Swashbuckle.FluentValidation" Version="7.1.6" />
<PackageReference Include="Swashbuckle.AspNetCore" Version="8.1.1" />
</ItemGroup>
</Project>
Program.cs
using FluentValidation;
using FluentValidation.AspNetCore;
using MicroElements.Swashbuckle.FluentValidation.AspNetCore;
var builder = WebApplication.CreateBuilder(args);
var services = builder.Services;
// Asp.Net stuff
services.AddControllers();
services.AddEndpointsApiExplorer();
// Add Swagger
services.AddSwaggerGen();
// Add FV
services.AddFluentValidationAutoValidation();
services.AddFluentValidationClientsideAdapters();
// Add FV validators
services.AddValidatorsFromAssemblyContaining<Program>();
// Add FV Rules to swagger
services.AddFluentValidationRulesToSwagger();
var app = builder.Build();
// Use Swagger
app.UseSwagger();
app.UseSwaggerUI();
app.MapControllers();
app.Run();
2. AspNetCore WebApi
Reference packages in your web project
<PackageReference Include="FluentValidation.AspNetCore" Version="11.3.1" />
<PackageReference Include="MicroElements.Swashbuckle.FluentValidation" Version="7.1.6" />
<PackageReference Include="Swashbuckle.AspNetCore" Version="8.1.1" />
Change Startup.cs
// This method gets called by the runtime. Use this method to add services to the container.
public void ConfigureServices(IServiceCollection services)
{
// Asp.net stuff
services.AddControllers();
// HttpContextValidatorRegistry requires access to HttpContext
services.AddHttpContextAccessor();
// Register FV validators
services.AddValidatorsFromAssemblyContaining<Startup>(lifetime: ServiceLifetime.Scoped);
// Add FV to Asp.net
services.AddFluentValidationAutoValidation();
// Add swagger
services.AddSwaggerGen(c =>
{
c.SwaggerDoc("v1", new OpenApiInfo { Title = "My API", Version = "v1" });
});
// [Optional] Add INameResolver (SystemTextJsonNameResolver will be registered by default)
// services.AddSingleton<INameResolver, CustomNameResolver>();
// Adds FluentValidationRules staff to Swagger. (Minimal configuration)
services.AddFluentValidationRulesToSwagger();
// [Optional] Configure generation options for your needs. Also can be done with services.Configure<SchemaGenerationOptions>
// services.AddFluentValidationRulesToSwagger(options =>
// {
// options.SetNotNullableIfMinLengthGreaterThenZero = true;
// options.UseAllOffForMultipleRules = true;
// });
// Adds logging
services.AddLogging(builder => builder.AddConsole());
}
// This method gets called by the runtime. Use this method to configure the HTTP request pipeline.
public void Configure(IApplicationBuilder app, IHostingEnvironment env)
{
app.UseRouting();
app.UseEndpoints(endpoints =>
{
endpoints.MapControllers();
});
// Adds swagger
app.UseSwagger();
// Adds swagger UI
app.UseSwaggerUI(c =>
{
c.SwaggerEndpoint("/swagger/v1/swagger.json", "My API V1");
});
}
Version compatibility
| MicroElements.Swashbuckle.FluentValidation | Swashbuckle.AspNetCore | FluentValidation |
|---|---|---|
| [1.1.0, 2.0.0) | [3.0.0, 4.0.0) | >=7.2.0 |
| [2.0.0, 3.0.0) | [4.0.0, 5.0.0) | >=8.1.3 |
| [3.0.0, 3.1.0) | [5.0.0, 5.2.0) | >=8.3.0 |
| [3.1.0, 4.2.1) | [5.2.0, 6.0.0) | >=8.3.0 |
| [4.2.0, 5.0.0) | [5.5.1, 7.0.0) | [9.0.0, 10) |
| [5.0.0, 6.0.0) | [6.3.0, 7.0.0) | [10.0.0, 12) |
| [7.0.0, 7.3.0) | [8.0.0, 11.0.0) | [11.0.0, 13) |
| [7.3.0, 8.0.0) | [8.0.0, 12.0.0), by TFM | [12.0.0, 13) |
.NET 8/9 use Swashbuckle 8.x / Microsoft.OpenApi 1.x; .NET 10 uses Swashbuckle 10.x / Microsoft.OpenApi 2.x; .NET 11 uses Swashbuckle 11.x / Microsoft.OpenApi 3.x. Select the matching target-framework asset; the net10 asset does not support Swashbuckle 11.
.NET 11 support — 7.3.0
Version 7.3.0 adds stable .NET 11 support (#236).
| Package | Target-framework assets | .NET 11 integration |
|---|---|---|
MicroElements.OpenApi.FluentValidation |
net8.0, net9.0, net10.0, net11.0 | Shared core used by the integrations below |
MicroElements.AspNetCore.OpenApi.FluentValidation |
net9.0, net10.0, net11.0 | Microsoft.AspNetCore.OpenApi 11.x / Microsoft.OpenApi 3.x; default OpenAPI 3.2 and explicitly selected 3.1, at runtime and build time |
MicroElements.Swashbuckle.FluentValidation |
net8.0, net9.0, net10.0, net11.0 | Dedicated net11 asset using stable Swashbuckle 11.0.1 / Microsoft.OpenApi 3.11.0; OpenAPI 3.2 generation with FV constraints |
MicroElements.NSwag.FluentValidation |
net8.0, net9.0 | Existing assets tested on a .NET 11 host with NSwag 14.4.0 / NJsonSchema 11.3.2; no dedicated net11 asset |
Swashbuckle 11 supports an explicit OpenAPI 3.2 selection in the middleware:
app.UseSwagger(options =>
options.OpenApiVersion = Microsoft.OpenApi.OpenApiSpecVersion.OpenApi3_2);
Numeric bounds: .NET 11 changes float/double-to-decimal conversion. Generated bounds can therefore have longer fractional values than on older runtimes: for example, a 5.1f lower bound is emitted as 5.099999904632568359375 rather than 5.1. The library preserves the runtime conversion result without additional rounding. Tests use exact runtime-specific expectations.
Release validation covers the .NET 8/9/10/11 test matrix, actual Swashbuckle middleware serialization, native OpenAPI 3.2/3.1 runtime and build-time generation, and Linux/Windows CI.
For source builds, global.json requires SDK 11.0.100 with rollForward: latestFeature: newer eligible 11.0 feature bands and patches are allowed without automatically selecting SDK 12. Package consumers need the SDK for their own target framework, rather than this repository's SDK baseline.
Sample application
See sample project: https://github.com/micro-elements/MicroElements.Swashbuckle.FluentValidation/tree/master/samples/SampleWebApi
Supported validators
- INotNullValidator (NotNull)
- INotEmptyValidator (NotEmpty)
- ILengthValidator (for strings: Length, MinimumLength, MaximumLength, ExactLength) (for arrays: MinItems, MaxItems)
- IRegularExpressionValidator (Email, Matches)
- IComparisonValidator (GreaterThan, GreaterThanOrEqual, LessThan, LessThanOrEqual)
- IBetweenValidator (InclusiveBetween, ExclusiveBetween)
File uploads (media types & size) — Issue #216
Validation rules written on nested IFormFile members (e.g. RuleFor(x => x.File.ContentType) /
RuleFor(x => x.File.Length)) are not reflected in the OpenAPI document: FluentValidation names them
File.ContentType / File.Length, which never match the flat File schema property, and Must(...) carries
no introspectable metadata. Use the dedicated File-level rules instead:
using MicroElements.OpenApi.FluentValidation.FileUpload;
public class UploadProductImageRequestValidator : AbstractValidator<UploadProductImageRequest>
{
public UploadProductImageRequestValidator()
{
RuleFor(x => x.File)
.NotNull() // required
.FileContentType("image/jpeg", "image/png") // allowed media types
.MaxFileSize(2 * 1024 * 1024); // 2 MB
}
}
These rules enforce the constraints at runtime and drive the OpenAPI output:
multipart/form-data:
schema:
properties:
File:
type: string
format: binary
description: "Allowed content types: image/jpeg, image/png. Maximum file size: 2097152 bytes."
encoding:
File:
contentType: "image/jpeg, image/png"
Available rules: .FileContentType(params string[]), .MaxFileSize(long), .MinFileSize(long),
.FileSizeBetween(long, long).
Backend support:
| Backend | size & content types in description |
machine-readable encoding.contentType |
|---|---|---|
| Swashbuckle | ✅ | ✅ (OpenAPI 3.0 by default, including net10) |
| NSwag | ✅ | ✅ via FluentValidationOperationProcessor (serialized as encodingType — a known NSwag limitation) |
| Microsoft.AspNetCore.OpenApi | ✅ | ✅ (net9 + net10) |
The issue scenario — making the generated OpenAPI document reflect the allowed content types and size limit — works on all three backends, both via the file part description and as the machine-readable encoding.contentType.
Notes:
- File size has no standard OpenAPI/JSON-Schema byte keyword, so it is documented in
descriptiononly (annotation, not enforced by consumers; enforcement stays server-side via FluentValidation). - NSwag requires registering the operation processor:
settings.OperationProcessors.Add(serviceProvider.GetService<FluentValidationOperationProcessor>())(see the NSwag sample). - Microsoft.AspNetCore.OpenApi: on net10 the file part is emitted as a
$refto a sharedIFormFilecomponent, so the size/content-typedescriptionis shared across allIFormFileendpoints (differing per-endpoint rules would accumulate there) — butencoding.contentTypeis per-operation and unaffected.
Extensibility
You can register FluentValidationRule in ServiceCollection.
User defined rule name replaces default rule with the same.
Full list of default rules can be get by FluentValidationRules.CreateDefaultRules()
List or default rules:
- Required
- NotEmpty
- Length
- Pattern
- Comparison
- Between
Example of rule:
new FluentValidationRule("Pattern")
{
Matches = propertyValidator => propertyValidator is IRegularExpressionValidator,
Apply = context =>
{
var regularExpressionValidator = (IRegularExpressionValidator)context.PropertyValidator;
context.Schema.Properties[context.PropertyKey].Pattern = regularExpressionValidator.Expression;
}
},
Samples
Swagger Sample model and validator
public class Sample
{
public string PropertyWithNoRules { get; set; }
public string NotNull { get; set; }
public string NotEmpty { get; set; }
public string EmailAddress { get; set; }
public string RegexField { get; set; }
public int ValueInRange { get; set; }
public int ValueInRangeExclusive { get; set; }
public float ValueInRangeFloat { get; set; }
public double ValueInRangeDouble { get; set; }
}
public class SampleValidator : AbstractValidator<Sample>
{
public SampleValidator()
{
RuleFor(sample => sample.NotNull).NotNull();
RuleFor(sample => sample.NotEmpty).NotEmpty();
RuleFor(sample => sample.EmailAddress).EmailAddress();
RuleFor(sample => sample.RegexField).Matches(@"(\d{4})-(\d{2})-(\d{2})");
RuleFor(sample => sample.ValueInRange).GreaterThanOrEqualTo(5).LessThanOrEqualTo(10);
RuleFor(sample => sample.ValueInRangeExclusive).GreaterThan(5).LessThan(10);
// WARNING: Swashbuckle implements minimum and maximim as int so you will loss fraction part of float and double numbers
RuleFor(sample => sample.ValueInRangeFloat).InclusiveBetween(1.1f, 5.3f);
RuleFor(sample => sample.ValueInRangeDouble).ExclusiveBetween(2.2, 7.5f);
}
}
Swagger Sample model screenshot

Validator with Include
public class CustomerValidator : AbstractValidator<Customer>
{
public CustomerValidator()
{
RuleFor(customer => customer.Surname).NotEmpty();
RuleFor(customer => customer.Forename).NotEmpty().WithMessage("Please specify a first name");
Include(new CustomerAddressValidator());
}
}
internal class CustomerAddressValidator : AbstractValidator<Customer>
{
public CustomerAddressValidator()
{
RuleFor(customer => customer.Address).Length(20, 250);
}
}
Nested objects (SetValidator / ChildRules)
Rules for a nested object are applied to the child component schema, and the parent property keeps a $ref to it. Both a standalone child validator (SetValidator) and inline ChildRules are supported (inline ChildRules $ref preservation was fixed in 7.1.6, see #198):
public class CreateUserRequest
{
public CreateUserParams User { get; set; }
}
public class CreateUserParams
{
public string Email { get; set; }
public string Name { get; set; }
}
public class CreateUserRequestValidator : AbstractValidator<CreateUserRequest>
{
public CreateUserRequestValidator()
{
// Inline child rules — no separate validator class required
RuleFor(x => x.User)
.NotEmpty()
.ChildRules(user =>
{
user.RuleFor(u => u.Email).NotEmpty().EmailAddress();
user.RuleFor(u => u.Name).NotEmpty().MaximumLength(510);
});
// Equivalent with a standalone validator:
// RuleFor(x => x.User).NotEmpty().SetValidator(new CreateUserParamsValidator());
}
}
The Email/Name constraints (and required) end up on the CreateUserParams component, while the parent stays a reference:
"CreateUserRequest": {
"required": [ "user" ],
"type": "object",
"properties": {
"user": { "$ref": "#/components/schemas/CreateUserParams" }
}
}
Get params bounded to validatable models
MicroElements.Swashbuckle.FluentValidation updates swagger schema for operation parameters bounded to validatable models.
Nested [FromQuery] parameters
When a [FromQuery] model has nested objects, ASP.NET Core flattens them into dot-path parameters (e.g. RequiredSubType.SubProperty). The validation rules for such a nested parameter are reflected in the OpenAPI document only when they are actually enforced at runtime:
- The nested validator must be wired from the root validator via
SetValidator/ChildRules(since 7.1.7). FluentValidation never auto-validates a child object just because a validator for it is registered in DI — so an unwired nested validator no longer leaksrequired/length/pattern constraints onto the parameter. - A nested parameter is marked
requiredonly when every ancestor segment of the dot-path is required (see #209).
Note: if there is no validator registered for the root
[FromQuery]type (only a leaf/child validator), the flattened nested parameter is left unconstrained — matching the default runtime, where no validation runs without a root validator. If you instead validate the child manually in the controller (e.g.new SubValidator().Validate(filter.Child)), those constraints cannot be detected statically and so are not reflected in the schema — register/wire a validator for the root type if you want them documented.
Document filter pipeline (UseDocumentFilter)
Since 7.2.0 the library offers a supported alternative pipeline: a single document filter instead of the default schema + operation filters.
services.AddFluentValidationRulesToSwagger(
configureRegistration: options => options.UseDocumentFilter = true);
The document filter processes the whole document at once — component schemas, operation parameters (including required-marking, #209), request bodies and encoding.contentType (#216) — and performs the unused-query-schema cleanup once at the end.
Why opt in: the default pipeline runs per operation, so a DTO shared between several endpoints (or between [FromQuery] and [FromBody] bindings) used to hit per-operation state bugs (#223, #226); those were fixed, but the net8.0/net9.0 targets keep a narrower guarantee (the healing API only exists in Swashbuckle 10+). Under the document filter this class of issue cannot occur, on any target framework.
Caveats:
- The default pipeline is unchanged —
UseDocumentFilteris opt-in. A future major version may make it the default. - On net10.0 the cleanup also clears Swashbuckle's internal reserved-ids for the container types it processed; transitively registered child schemas are not covered. On net8.0/net9.0, a custom
IDocumentFilterregistered after this one that regenerates a removed[FromQuery]container type may still observe a reserved-but-removed schema state. ExperimentalUseDocumentFilterstill works as an obsolete alias and forwards toUseDocumentFilter.
The samples/MinimalApi sample runs on this pipeline.
Defining rules dynamically from database
See BlogValidator in sample.
Common problems and workarounds
Error: System.InvalidOperationException: 'Cannot resolve 'IValidator<T>' from root provider because it requires scoped service 'TDependency'
Workarounds in order or preference:
Workaround 1 (Use HttpContextServiceProviderValidatorFactory) by @WarpSpideR
public void ConfigureServices(IServiceCollection services)
{
// HttpContextServiceProviderValidatorFactory requires access to HttpContext
services.AddHttpContextAccessor();
services
.AddMvc()
// Adds fluent validators to Asp.net
.AddFluentValidation(c =>
{
c.RegisterValidatorsFromAssemblyContaining<Startup>();
// Optionally set validator factory if you have problems with scope resolve inside validators.
c.ValidatorFactoryType = typeof(HttpContextServiceProviderValidatorFactory);
});
Workaround 2 (Use ScopedSwaggerMiddleware)
Replace UseSwagger for UseScopedSwagger:
public void Configure(IApplicationBuilder app, IHostingEnvironment env)
{
app
.UseMvc()
// Use scoped swagger if you have problems with scoped services in validators
.UseScopedSwagger();
Workaround 3 (Set ValidateScopes to false)
public static IWebHost BuildWebHost(string[] args) =>
WebHost.CreateDefaultBuilder(args)
// Needed for using scoped services (for example DbContext) in validators
.UseDefaultServiceProvider(options => options.ValidateScopes = false)
.UseStartup<Startup>()
.Build();
Problem: I cant use several validators of one type
Example: You split validator into several small validators but AspNetCore uses only one of them.
Workaround: Hide dependent validators with internal and use Include to include other validation rules to one "Main" validator.
Problem: I'm using FluentValidation or FluentValidation.DependencyInjectionExtensions instead of FluentValidation.AspNetCore
If you are using the more basic FluentValidation or FluentValidation.DependencyInjectionExtensions libraries, then they will not automatically register IValidatorFactory and you will get an error at runtime: "ValidatorFactory is not provided. Please register FluentValidation." In that case you must register it manually (see issue 97 for more details):
services.TryAddTransient<IValidatorFactory, ServiceProviderValidatorFactory>();
services.AddFluentValidationRulesToSwagger();
Problem: Newtonsoft.Json DefaultNamingStrategy, SnakeCaseNamingStrategy does not work
Startup.cs:
.AddJsonOptions(options =>
{
options.JsonSerializerOptions.PropertyNamingPolicy = new NewtonsoftJsonNamingPolicy(new SnakeCaseNamingStrategy());
//options.JsonSerializerOptions.DictionaryKeyPolicy = new NewtonsoftJsonNamingPolicy(new SnakeCaseNamingStrategy());
})
/// <summary>
/// Allows use Newtonsoft <see cref="NamingStrategy"/> as System.Text <see cref="JsonNamingPolicy"/>.
/// </summary>
public class NewtonsoftJsonNamingPolicy : JsonNamingPolicy
{
private readonly NamingStrategy _namingStrategy;
/// <summary>
/// Creates new instance of <see cref="NewtonsoftJsonNamingPolicy"/>.
/// </summary>
/// <param name="namingStrategy">Newtonsoft naming strategy.</param>
public NewtonsoftJsonNamingPolicy(NamingStrategy namingStrategy)
{
_namingStrategy = namingStrategy;
}
/// <inheritdoc />
public override string ConvertName(string name)
{
return _namingStrategy.GetPropertyName(name, false);
}
}
Credits
Initial version of this project was based on Mujahid Daud Khan answer on StackOverflow: https://stackoverflow.com/questions/44638195/fluent-validation-with-swagger-in-asp-net-core/49477995#49477995
$# Changes in 7.2.3
- Fixed: constraints inside
ChildRules(child => child.RuleFor(x => x).Matches(...).DependentRules(...))were missing from the parent property's OpenAPI schema. Identity child rules now contribute their constraints to the owning property (or collection item), including nested identity validators, while honoring rule/component filters and conditional-rule settings. The fix is shared by Swashbuckle, NSwag, and Microsoft.AspNetCore.OpenApi. Runtime validation is unchanged; schema generation does not executeMustpredicates or repository lookups, and does not infer constraints fromDependentRules. - Fixed: identity child
NotNull/NotEmptyrules preserve the owning property's nullability and optionality, matching FluentValidation's null-skipping child adapters. Non-empty string/array constraints and explicit parent presence rules are preserved.
Changes in 7.2.2
- Fixed:
MicroElements.AspNetCore.OpenApi.FluentValidationdid not apply FluentValidation rules to a[FromForm]DTO bound by an MVC controller action (Issue #232, follow-up to the Swashbuckle-only #170 fix)- Root cause: MVC
ApiExplorerflattens a controller's[FromForm]complex parameter into one form field per property, soMicrosoft.AspNetCore.OpenApibuilds the request body as an inline schema from those descriptions and never asks for the DTO'sJsonTypeInfo—FluentValidationSchemaTransformertherefore never saw the type. Minimal API form bodies are not flattened and were never affected - Fix:
FluentValidationOperationTransformernow applies the DTO's rules to the inline form schema for bothmultipart/form-dataandapplication/x-www-form-urlencoded. The flattening is detected viaModelMetadata.ContainerTypeon the form-bound parameter descriptions, so a minimal API body — which the schema transformer already owns — is never touched twice - Property keys are taken verbatim from the schema, because a flattened form field is named after the model binder (
Name, notname); the validator-side match stays name-insensitive - An action binding more than one form parameter composes its body as an
allOfof one property bag per parameter; every bag is now constrained, and each bag is paired with the parameter that owns its fields — including the parameters the action binds directly (a loose scalar, array orIFormFile), which get a bag of their own but no rules. Without that pairing a DTO could be pulled into a foreign bag by a single coinciding field name and lose the constraints on its own bag encoding.contentType(Issue #216) is now also emitted when the file part sits inside such anallOfbag- Dotted keys (
Inner.City, ApiExplorer's binding path for a nested complex property) are skipped: the name matcher ignores separators, so such a key would otherwise inherit the rules of an unrelated root property namedInnerCity. Nested form fields remain unsupported, matching the Swashbuckle form path - Issue #216
encoding.contentTypeis unchanged for the shapes it already covered, and now also consults every validator in multi-validator mode (IsOneValidatorForType = false) instead of only the first - Known limitations on this path (unchanged by this fix): a renamed form field (
[FromForm(Name = "...")], or a property renamed by theINameResolver) gets no constraints, and on net10 a form part rendered as a$ref(IFormFile, enums) cannot receive property-level constraints - Thanks to @bux for the report
- Root cause: MVC
Changes in 7.2.1
- Fixed: the document-filter pipeline (
UseDocumentFilter = true) did not apply FluentValidation constraints to aliased operation parameters such as[FromHeader(Name = "X-Correlation-Id")](Issue #230). The constraint copy now uses the resolved schema property key (kebab-case/camelCase/PascalCase aliases) and falls back to theINameResolverfor renames beyond separators (e.g.[JsonPropertyName]) — full parity with the operation filter - Fixed: a dot in a header name (
[FromHeader(Name = "X.Trace.Id")]— legal in HTTP) was treated as a nested[FromQuery]dot-path (#209/#211) and silently dropped the header's validation rules. Header-bound parameters are now exempt from the dot-path logic in all three parameter pipelines:FluentValidationOperationFilter,FluentValidationDocumentFilterand the ASP.NET CoreFluentValidationOperationTransformer. NSwag is unaffected (it has no dot-path parameter logic) - Fixed: the document filter matched document parameters to
ApiExplorerdescriptions case-sensitively, so options likeDescribeAllParametersInCamelCasemade it skip required-marking and constraint copying. The lookup is now case-insensitive, matching the operation filter - Thanks to @jgarciadelanoceda for the report and the repro
Changes in 7.2.0
- Added: the document-filter pipeline is promoted from experimental to a supported opt-in (
RegistrationOptions.UseDocumentFilter, defaultfalse). The document filter processes the whole document at once and performs the unused-query-schema cleanup once at the end, so per-operation shared-DTO state issues (#223/#226) cannot occur in this pipeline — on all target frameworks, including net8.0/net9.0 where the 7.1.11 healing API is unavailable- Full functional parity with the default schema + operation filter pipeline: required-marking with the whole-dot-path check (#209), request bodies and
encoding.contentTypefor[FromForm](#216), multi-validator support,allOf/oneOf/anyOftraversal,$refpreservation for unmodified properties (#198, net10.0), and every operation of a multi-verb path is now processed (previously only the first) - The #209 and #216 logic is extracted into internal components shared by both pipelines, so they cannot drift apart
- Robustness: the filter no longer fails the whole document generation on a throwing validator (top-level try/catch), falls back to
ServiceProviderValidatorRegistrylike the sibling filters, honors an injectedIFluentValidationRuleProvider(new optional constructor parameter, appended last — source-compatible), and had its dead code, logging and nullability issues cleaned up. Behavior note: constructingFluentValidationDocumentFilterwith neithervalidatorRegistrynorserviceProvidernow throwsArgumentNullException(matching the sibling filters) instead of silently producing a filter that applies no rules; the DI registration path is unaffected - On net10.0 the cleanup also heals Swashbuckle's reserved-ids for processed container types (
SchemaRepository.ReplaceSchemaId), so custom document filters running afterwards can regenerate them ExperimentalUseDocumentFilterstill works as an[Obsolete]alias forwarding toUseDocumentFilter- The default pipeline is unchanged; a future major version may switch the default
samples/MinimalApinow runs on the document-filter pipeline; README documents the option and its caveats
- Full functional parity with the default schema + operation filter pipeline: required-marking with the whole-dot-path check (#209), request bodies and
Changes in 7.1.11
- Fixed: a DTO shared between a flattened
[FromQuery]/[AsParameters]binding and a request body ([FromBody]/[FromForm]) in the same document could lose its FluentValidation rules, and the emitted document could contain a$refto a removed component (Issue #226). net10.0 target only- Root cause: the Issue #180 cleanup left the container type "reserved-but-removed" in Swashbuckle's
SchemaRepository(component removed, internal reserved-id kept). The 7.1.10 fix (#223) recovered the schema for reading constraint values, but a later[FromBody]/[FromForm]operation binding the same type made Swashbuckle emit a$refto a component that no longer exists (confirmed empirically), and rules applied on the recovered throwaway instance never reached the document - Fix (net10.0 / Swashbuckle 10.x): the Issue #180 cleanup now heals the repository state via
SchemaRepository.ReplaceSchemaId(public API since Swashbuckle 10.1.0) before removing a side-effect schema — the reservation is cleared together with the component, so the next operation binding the same type regenerates a full component and the rules reach the real document object.SwashbuckleSchemaProvidertracksType → schemaIdfor everyGetSchemaForTypecall (including the Issue #209 ancestor walk) to make the healing possible - net8.0/net9.0 keep the 7.1.10 behavior: they pin Swashbuckle 8.1.1 where
ReplaceSchemaIddoes not exist, and bumping the minimum would force the Microsoft.OpenApi 2.x breaking change on consumers. The throwaway recovery from #223 remains as a safety net on all targets - Thanks to @jgarciadelanoceda for suggesting the
ReplaceSchemaIdapproach
- Root cause: the Issue #180 cleanup left the container type "reserved-but-removed" in Swashbuckle's
Full release notes can be found at: https://github.com/micro-elements/MicroElements.Swashbuckle.FluentValidation/blob/master/CHANGELOG.md
-
.NETFramework 10.0
- MicroElements.OpenApi.FluentValidation (>= 7.2.3)
- Microsoft.AspNetCore.OpenApi (>= 10.0.0 && < 11.0.0)
-
.NETFramework 9.0
- MicroElements.OpenApi.FluentValidation (>= 7.2.3)
- Microsoft.AspNetCore.OpenApi (>= 9.0.0 && < 10.0.0)
- .NETFramework 9.0: 9.0.0.0
- .NETFramework 10.0: 10.0.0.0
OwnersAlexey Petryashev |
Authorsalexey.petriashev, MicroElements |
Project URLhttps://github.com/micro-elements/MicroElements.Swashbuckle.FluentValidation |
LicenseMIT |
TagsOpenApi FluentValidation aspnetcore Microsoft.AspNetCore.OpenApi |
Info106 total downloads |
| 3 downloads for version 7.2.3 |
| Download (139.08 KB) |
| Found on the current feed only |
Package history
| Version | Size | Last updated | Downloads | Mirrored? | |||
|---|---|---|---|---|---|---|---|
|
|
7.3.1 | 134.06 KB | Sat, 21 Nov 2026 19:08:05 GMT | 3 |
|
||
|
|
7.3.0 | 134.54 KB | Sat, 14 Nov 2026 07:53:47 GMT | 3 |
|
||
|
|
7.3.0-beta.1 | 134.99 KB | Sat, 31 Oct 2026 19:52:38 GMT | 3 |
|
||
|
|
7.2.4 | 138.98 KB | Tue, 03 Nov 2026 14:22:54 GMT | 5 |
|
||
|
|
7.2.3 | 139.08 KB | Sat, 31 Oct 2026 09:40:48 GMT | 3 |
|
||
|
|
7.2.2 | 139.08 KB | Fri, 21 Aug 2026 06:19:47 GMT | 7 |
|
||
|
|
7.2.1 | 131.31 KB | Mon, 13 Jul 2026 11:11:12 GMT | 3 |
|
||
|
|
7.2.0 | 131.01 KB | Sun, 12 Jul 2026 20:40:46 GMT | 5 |
|
||
|
|
7.1.11 | 130.4 KB | Sun, 12 Jul 2026 12:35:59 GMT | 3 |
|
||
|
|
7.1.10 | 130.52 KB | Sun, 12 Jul 2026 10:16:22 GMT | 3 |
|
||
|
|
7.1.9 | 131.1 KB | Thu, 09 Jul 2026 07:20:36 GMT | 5 |
|
||
|
|
7.1.8 | 131.56 KB | Wed, 01 Jul 2026 19:15:27 GMT | 3 |
|
||
|
|
7.1.8-beta.2 | 131.51 KB | Sun, 21 Jun 2026 10:40:51 GMT | 3 |
|
||
|
|
7.1.8-beta.1 | 128.53 KB | Sat, 20 Jun 2026 17:47:10 GMT | 3 |
|
||
|
|
7.1.7 | 123.88 KB | Sat, 20 Jun 2026 12:54:06 GMT | 3 |
|
||
|
|
7.1.7-beta.3 | 123.95 KB | Wed, 17 Jun 2026 20:24:28 GMT | 4 |
|
||
|
|
7.1.7-beta.2 | 120.32 KB | Wed, 17 Jun 2026 13:00:49 GMT | 3 |
|
||
|
|
7.1.7-beta.1 | 119.08 KB | Mon, 15 Jun 2026 17:28:38 GMT | 3 |
|
||
|
|
7.1.6 | 119.18 KB | Tue, 02 Jun 2026 16:35:34 GMT | 7 |
|
||
|
|
7.1.6-beta.1 | 118.73 KB | Tue, 02 Jun 2026 13:24:54 GMT | 3 |
|
||
|
|
7.1.5-beta.2 | 118.91 KB | Sat, 16 May 2026 12:15:38 GMT | 3 |
|
||
|
|
7.1.5-beta | 117.74 KB | Wed, 01 Apr 2026 12:10:38 GMT | 3 |
|
||
|
|
7.1.4 | 117.01 KB | Sun, 29 Mar 2026 16:07:39 GMT | 3 |
|
||
|
|
7.1.4-beta | 117.03 KB | Tue, 24 Mar 2026 12:10:42 GMT | 3 |
|
||
|
|
7.1.3 | 108.97 KB | Tue, 24 Mar 2026 08:01:05 GMT | 3 |
|
||
|
|
7.1.2 | 109 KB | Mon, 09 Mar 2026 21:49:01 GMT | 3 |
|
||
|
|
7.1.1 | 108.69 KB | Mon, 09 Mar 2026 19:22:03 GMT | 3 |
|
||
|
|
7.1.0 | 98.38 KB | Mon, 09 Mar 2026 15:09:16 GMT | 3 |
|
||
|
|
7.1.0-beta.2 | 98.45 KB | Fri, 06 Mar 2026 08:23:02 GMT | 3 |
|
||
|
|
7.1.0-beta.1 | 98.43 KB | Thu, 26 Feb 2026 20:30:45 GMT | 4 |
|