MicroElements.Swashbuckle.FluentValidation 4.0.0-rc.1

$# Changes in 4.0.0-rc.1: * FluentValidation updated to [9.0.0-preview5, 10) * Swashbuckle.AspNetCore updated to [5.4.1, 6) * Changed getting included validator (FluentValidation internal API changed) * New EmailValidator rule compatible with FluentValidation AspNetCoreCompatibleEmailValidator # Changes in 3.2.0: * FluentValidation fix version to [8.3.0, 9) * Swashbuckle.AspNetCore fix version to [5.2.0, 6) * Base type for numeric switched to decimal to match type change in OpenApi. Fixes floating numbers with nines after period. * More smart MinLength, MaxLength, Minimum, Maximum that allows to combine rules without override values. * More strict limits will be used for min and max values that was set more then once in other rules # Changes in 3.1.1: * Mark required properties as not nullable (PR#58 by @manne) Fixes: #55, #57 # Changes in 3.1.0: * Swashbuckle.AspNetCore updated to version >= 5.2.0 * Fixed: #53 (Missing method exception when using Swashbuckle > 5.0.0) # Changes in 3.0.0: * Supports Swashbuckle 5, net core 3 and brand new System.Text.Json * Swashbuckle.AspNetCore updated to version >= 5.0.0 (new Microsoft.OpenApi) * FluentValidation updated to version >= 8.3 * FluentValidation property rules of type CollectionValidationRules (RuleForEach()) are no longer exposed #49. * New IgnoreAllStringComparer was invented to solve problem with different property name formatting: camelCase, PascalCase, snake_case, kebab-case * Added NewtonsoftJsonNamingPolicy example to override property name formatting in new System.Text.Json according Newtonsoft.Json.Serialization.NamingStrategy (see: SampleWebApi) * Fixed invalid documentation on validation rules containing a condition #38 * Fixed: #37 (FluentValidationOperationFilter now uses swachbuckle interface to determine json settings) Full release notes can be found at: https://github.com/micro-elements/MicroElements.Swashbuckle.FluentValidation.git/blob/master/CHANGELOG.md