MicroElements.Swashbuckle.FluentValidation 5.1.0-rc.2

$# Changes in 5.1.0: * Use new registration method AddFluentValidationRulesToSwagger instead of AddFluentValidationRules to allow all feature set * AddFluentValidationRules become obsolete * Added ability to set ServiceLifetime in AddFluentValidationRulesToSwagger, default value: Scoped. Fixes #83 * Turned off test rule BeforeAll. Fixes #87 * More detailed warnings in FluentValidationRulesScopeAdapter * Added detailed error on getting absent property by name # Changes in 5.0.0: * FluentValidation updated to 10.0.0 * Swashbuckle.AspNetCore updated to 6.0.0 * RuleContext: Obsolete SchemaFilterContext replaced with ReflectionContext (removed dependency on Swashbuckle) * Dependency Swashbuckle.AspNetCore changed to Swashbuckle.AspNetCore.SwaggerGen which is UI independent (PR#82 by buvinghausen) * Added INameResolver to resolve names. Issue #80 * Added AddFluentValidationRulesToSwagger extensions to simplify registration * FluentValidationSwaggerGenOptions renamed to SchemaGenerationOptions, IsAllOffSupported renamed to UseAllOffForMultipleRules # Changes in 4.3.0: * Fixed #79: Adding a simple Length validation to a string field should not make the field non-nullable * Fixed #76: SetValidator is applying FluentValidation rules to parent object property with same name # Changes in 4.2.0: * Swashbuckle.AspNetCore version supports up to 7 (PR#75 by fabich) # Changes in 4.1.0: * RuleForEach supported. Issue #66 * SetValidator supported. Issue #68 * Multiple match rules supported with allOf. Issue #69 * Fixed #67: Absence of MinimumLength should not override nullable. (PR#67 by bcronje) * Fixed #70: Nullability for numerics if MinLength is greater then zero * Nullable annotations added Full release notes can be found at: https://github.com/micro-elements/MicroElements.Swashbuckle.FluentValidation/blob/master/CHANGELOG.md