Stable release 7.1.7 — promotes 7.1.7-beta.3 to stable.
Fixed
- Nested
[FromQuery]fixes (#209 + #211) now also apply to the nativeMicrosoft.AspNetCore.OpenApitransformer and the experimental Swashbuckle DocumentFilter (Issue #213)FluentValidationOperationTransformernow follows the same reachability + ancestor-required rules as the SwashbuckleOperationFilter- The experimental
FluentValidationDocumentFilterno longer copies value constraints onto a flattened nested parameter whose nested validation is not wired from the root validator GetMethodInfonow resolves the action method fromControllerActionDescriptor(MVC controllers), not only minimal-API endpoint metadata- NSwag is unaffected (it has no
[FromQuery]parameter flattening)
- A validator for a nested type bound via
[FromQuery]was reflected in the OpenAPI document even when it was not wired into the root validator viaSetValidator/ChildRules(Issue #211)- Nested rules are now applied only when the
SetValidator/ChildRuleschain from the action's root[FromQuery]validator actually reaches the leaf container - Behavioral change: when no validator is registered for the root
[FromQuery]type, a flattened nested parameter is left unconstrained — matching runtime
- Nested rules are now applied only when the
- A required leaf property inside an optional nested type bound via
[FromQuery]was wrongly marked as a required parameter (Issue #209)- A flattened nested parameter is now marked
requiredonly when every ancestor segment of the dot-path is required - Value constraints (e.g.
minLength) still apply to an optional nested parameter when it is provided
- A flattened nested parameter is now marked
Full changelog: CHANGELOG.md