Bump FluentValidation.AspNetCore from 8.5.0 to 9.0.1

[dependabot-preview]

Bumps FluentValidation.AspNetCore from 8.5.0 to 9.0.1.

Release notes

Sourced from FluentValidation.AspNetCore's releases.

9.0.0

Release notes

FluentValidation 9 is a major release and includes several breaking changes. Please read the upgrade guide for full details

Changes in 9.0.0

• ASP.NET core auto-validation can now be completely disabled while preserving clientside integration
• Types can now be filtered/skipped when auto-registering with the container
• Service lifetime is now configurable when auto-registering with the container

Changes in 9.0-preview5

• Remove IValidator.Validate(object) overload to improve typesafety (use a context if you need to preserve this behaviour)
• Replace non-generic ValidationContext class with IValidationContext interface
• ChildValidatorAdaptor and IncludeRule now require a generic type parameter indicating the root type being validated
• Expression accessors for comparison properties are now cached where possible
• {ComparisonProperty} placeholder now passes through the same logic as the {PropertyName} placeholder for consistency

Changes in 9.0-preview4

• {CollectionIndex} placeholder can now be accessed in child validators
• Additional ValidationException constructor that allows customising the default message.
• ScalePrecisionValidator algorithm now more consistent with SQL server (#1356)
• Add Icelandic translations of default messages (#1362)
• Additional When predicate overload that takes a ValidationContext
• Fixes to range clientside validators when using datetimes (#1371)
• Drop unsupported .NET Core versions from platform list

Changes in 9.0-preview3

• ASP.NET Core validator provider is now public
• Ensure ASP.NET Core providers aren't registered twice
• SoureLink integration
• Additional overload of SetValidator that receives property value in callback
• PropertyRule.ApplySharedCondition is now public
• Remove lowercase placeholders from ScalePrecisionValidator

Changes in 9.0-preview2

• Transform can now be used to transform a property value to another type prior to validation occurring
• Added WithMessageArgument to test helper extensions
• Added Slovenian translations of default error messages.
• Fixes/better handling of the non-generic overloads of AbstractValidator.Validate
• Removed the deprecated FluentValidation.Internal.Comparer
• TrackingCollection has been marked as internal
• Updated to latest version of Microsoft.NETFramework.ReferenceAssemblies for building net4x targets on non-windows platforms.

Changes in 9.0-preview1

Changelog

Sourced from FluentValidation.AspNetCore's changelog.

9.0.1 - 14 July 2020 Fix assembly version was still 8.

9.0 - 6 July 2020 Removed support for netstandard1.1, netstandard1.6 and net45 (net461 still supported) Removed support for unsupported .NET Core versions (2.2 and 3.0). LTS versions are supported (2.1 and 3.1) Default email validation mode now uses the same logic as ASP.NET Core. Previous regex behaviour is opt-in. TestHelper advanced mode now has more features (see https://docs.fluentvalidation.net/en/latest/testing.html#advanced-test-extensions) Equal/NotEqual now perform ordinal comparison when used with string properties Severity can now be set dynamically with a callback Removed WithLocalizedMessage (WithMessage that takes a callback is the replacement) Removed ResourceName from ValidationFailure Removed ResourceName and ResourceType from IStringSource. Removed SetCollectionValidator which was deprecated in 8.0 Removed DelegatingValidator which was deprecated in 8.x. Additional overload of OnAnyFailure that can receive a collection of validation failures Remove DisplayAttribute integration and reference to DataAnnotations. ComparisonProperty placeholder is now formatted like PropertyName Translations of default error messages into other languages are now lazily-loaded PropertyValidator.ShouldValidateAsync reanamed to ShouldValidateAsynchronously to remove confusion where the naming suggested this was an async method PropertyValidatorContext.Instance renamed to InstanceToValidate for consistency with ValidationContext. Removed various methods from MessageFormatter that were deprecated in 8.x Added Slovenian translations of default error messages. Added Icelandic translations of default error messages. Added WithMessageArgument to the test helpers. Transform can now be used to transform property values to other types. FluentValidationModelValidatorProvider and FluentValidationModelValidator are now public. Add additional overload of SetValidator that takes a Func that receives the current property value. Work around a bug in ASP.NET Core's integration testing components that can cause ConfigureServices to run multiple times. SourceLink integration. {CollectionIndex} placeholder can now be accessed in child validators. Additional ValidationException constructor that allows using both the default message and a custom one together. ScalePrecisionValidator algorithm now matches SQL Server. Additional overload of the When methods that contain the validation context. Automatically scanned types can be excluded when calling RegisterValidatorsFromAssemblyContaining in ASP.NET Core projects. New AutomaticValidationEnabled property for use in ASP.NET Core projects (defaults to true).

8.6.2 - 29 February 2020 Fix CollectionIndex placeholder not working with async workflow.

8.6.1 - 28 December 2019 Add explicit netcoreapp3.1 target to ASP.NET Core integration.

8.6.0 - 4 December 2019 Add support for ASP.NET Core 3.1 Fixed issue with property indexers being incorrectly stripped out when using test extensions. AddToModelState no longer includes a dot if PropertyName is null

8.5.1 - 2 November 2019 Ensure lazily loaded calls to WithMessage can be used for client-side validation, provided they don't attempt to access model properties from inside the delegate (eg when using IStringLocalizer).

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)