Pipeline-ruleset interaction

System Details

• FluentValidation version: 8.1.3
• Web Framework version ASP.NET Core 2.2 + netstandard2.0

Issue Description

I’d like to do something like an IValidatorInterceptor, but I’d like it cross cutting for the entire ASP.NET Core project.

Specifically, rather than using CustomizeValidatorAttribute or implementing IValidatorInterceptor on my validating class, instead put something into the pipeline which enables or disables a particular ruleset when a PATCH verb is encountered.

Is there a way to do this?

[JeremySkinner]

I had to push out an 8.2.1 release with an unrelated fix, so I made the IValidatorInterceptor change while I was in there. You can now register a default IValidatorInterceptor with the container, and it’ll be used for all requests.

Thinking out loud, it might be cool to have more extensibility points within the ASP.NET Core area of your code, especially maybe some DI dependency. What do you think?

If you have some specific requests, please could you open separate issues for them? Thanks.

[JeremySkinner]

Hmm not as simple as that, as context.Selector is (reasonably) a read only property…

The usual approach is to create a new instance of the context, copying across what you need from the old one (and providing a new selector). This is how the internal validators handle this.