MicroElements.OpenApi.FluentValidation 7.3.0

• net10.0

  • FluentValidation (>= 12.0.0)

• net11.0

  • FluentValidation (>= 12.0.0)

• net8.0

  • FluentValidation (>= 12.0.0)
  • Microsoft.Extensions.Logging.Abstractions (>= 9.0.5)
  • Microsoft.Extensions.Options (>= 9.0.5)

• net9.0

  • FluentValidation (>= 12.0.0)

$# Changes in 7.3.0
- Added: stable `net11.0` assets for the shared core, native ASP.NET Core OpenAPI adapter, and Swashbuckle adapter. The net11 Swashbuckle asset uses stable Swashbuckle 11.0.1 / Microsoft.OpenApi 3.11.0 and supports explicitly selected OpenAPI 3.2. Existing net8/net9/net10 Swashbuckle dependency families are preserved.
- Added: native OpenAPI 3.2 and explicitly selected 3.1 coverage at runtime and build time, preserving FluentValidation constraints on properties, child validators, collection items, parameters, forms, and shared schemas. .NET 11 dependencies and SDK baseline now use GA versions.
- Security: the native net10 adapter requires Microsoft.OpenApi 2.7.5 or later, excluding versions affected by GHSA-v5pm-xwqc-g5wc.
- Behavior: .NET 11 float/double bounds preserve the runtime's decimal conversion values without extra library rounding. Existing .NET 8–10 behavior and NSwag package targets are retained; existing NSwag assets are tested on a .NET 11 host.
- Includes the 7.2.4 fix for untyped string length constraints (#238). Source builds require SDK 11.0.100 or an eligible newer 11.0 feature band. MyGet publication is manual and restricted to the release tag.

# Changes in 7.3.0-beta.1
- Security: the native ASP.NET Core OpenAPI adapter now requires `Microsoft.OpenApi` 2.7.5 or later on net10, excluding versions affected by GHSA-v5pm-xwqc-g5wc.
- Added: `net11.0` assets for `MicroElements.OpenApi.FluentValidation` and `MicroElements.AspNetCore.OpenApi.FluentValidation`, using .NET 11 RC3 dependencies. The native ASP.NET Core adapter supports OpenAPI 3.2 and explicitly selected OpenAPI 3.1, with runtime and build-time generation coverage.
- Compatibility: Swashbuckle and NSwag retain their existing package targets and generator dependencies. Their existing assets were tested in .NET 11 hosts. This beta does not include the separate Swashbuckle 11 / Microsoft.OpenApi 3.x experiment.
- Behavior: on .NET 11, float and double validation bounds can appear with additional decimal digits in generated schemas because of runtime numeric conversion changes. The library preserves the runtime values without additional rounding; existing .NET 8–10 behavior is unchanged.
- Development: added a shared .NET 11 RC3 SDK baseline with `rollForward: latestFeature`. Package consumers do not need this SDK unless targeting .NET 11. Automatic package upload remains disabled; beta publication requires a manually triggered workflow on the beta tag.

# Changes in 7.2.4
- Fixed: `MicroElements.AspNetCore.OpenApi.FluentValidation` could lose string `minLength` and `maxLength` constraints when a custom JSON converter left the property's schema type unset (Issue #238, regression in 7.2.3). Length rules now fall back to the FluentValidation target's CLR string type only when the schema type is absent, preserving explicit schema types and the non-string `ChildRules` safeguards. A later transformer can restore the schema type without requiring registration order changes.
- Added regression coverage for string converters, late type restoration, identity child rules, explicit non-string schema types, and untyped non-string values.

# 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 execute `Must` predicates or repository lookups, and does not infer constraints from `DependentRules`.
- Fixed: identity child `NotNull`/`NotEmpty` rules 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.FluentValidation` did 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 `ApiExplorer` flattens a controller's `[FromForm]` complex parameter into one form field per property, so `Microsoft.AspNetCore.OpenApi` builds the request body as an **inline** schema from those descriptions and never asks for the DTO's `JsonTypeInfo` — `FluentValidationSchemaTransformer` therefore never saw the type. Minimal API form bodies are not flattened and were never affected
 - Fix: `FluentValidationOperationTransformer` now applies the DTO's rules to the inline form schema for both `multipart/form-data` and `application/x-www-form-urlencoded`. The flattening is detected via `ModelMetadata.ContainerType` on 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`, not `name`); the validator-side match stays name-insensitive
 - An action binding more than one form parameter composes its body as an `allOf` of 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 or `IFormFile`), 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 an `allOf` bag
 - 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 named `InnerCity`. Nested form fields remain unsupported, matching the Swashbuckle form path
 - Issue #216 `encoding.contentType` is 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 the `INameResolver`) 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


Full release notes can be found at: https://github.com/micro-elements/MicroElements.Swashbuckle.FluentValidation/blob/master/CHANGELOG.md