Add option to configure ValidationContext #254
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR adds a new
ConfigureContext
parameter toFluentValidationValidator
. This parameter allows users to pass anAction
to modify theValidationContext
before it is passed to FluentValidation validators.This solves the issue in #183, also addressed in #156, but instead of just allowing you to set RootContextData, it provides more robust access to ValidationContext configuration.
Why is this needed?
Currently, Blazored.FluentValidation does not provide a way to customize the
ValidationContext
used when validating a model. FluentValidation provides powerful context features, that Blazor users could make use of.Why is this better than just allowing
RootContextData
?RootContextData
is static per validation execution, whileConfigureContext
allows for dynamic modifications.ValidationContext<T>
contains more than justRootContextData
—it also allows setting a custom selector or defining a property chain.RootContextData
alone would be insufficient.Example Usage
This ensures that validators can access
UserRole
dynamically during validation.Unit tests of this feature are also included in the PR.