You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Changes in 7.1.1
Fixed: Nested object validation not applied for [FromQuery] parameters (Issue #162)
When Swashbuckle decomposes [FromQuery] models with nested objects into flat parameters (e.g., operation.op), the full dot-path name was used for schema property matching instead of the leaf name (op)
EqualsIgnoreAll("operation.op", "op") compared "OPERATIONOP" vs "OP" and failed to match
Strip dot-path prefix using LastIndexOf('.') in both FluentValidationOperationFilter and FluentValidationDocumentFilter
Supports arbitrarily deep nesting (e.g., a.b.c → c)
Added:SetNotNullableIfMinimumGreaterThenZero option to separately control nullable behavior for numeric Minimum constraints (Issue #154, ported from vchirikov fork PR #2)
Distinct from existing SetNotNullableIfMinLengthGreaterThenZero (for string MinLength)
Default: false (backward compatible)
Fixed:SetNotNullableIfMinLengthGreaterThenZero option now works in NSwag provider (Issue #154)
NSwagFluentValidationRuleProvider now accepts IOptions<SchemaGenerationOptions>
Rules NotEmpty, Length, Comparison, Between respect both nullable options
Feature parity across Swashbuckle, AspNetCore.OpenApi, and NSwag providers
Improved: Comparison/Between rules now use SetNotNullableIfMinimumGreaterThenZero() which checks actual Minimum value instead of unconditionally setting not-nullable