Complex property validation always happening?

Preempting this issue with the fact that I could be misunderstanding everything. My FluentValidation.Mvc dll is version 6.2.1.

This situation is actually very close to the complex properties example in the docs:

public class Foo {
    public string Identifier { get; set; }
    public Bar MainBar { get; set; }
    public Bar AlternateBarOne { get; set; }
    public Bar AlternateBarTwo { get; set; }
}

public class Bar {
    public string BarNumber { get; set; }
    public BarEnum BarType { get; set; }
}

public class BarValidator : AbstractValidator<Bar> {
    public BarValidator() {
        RuleFor(x => x.BarNumber).NotEmpty();
    }
}

public class FooValidator : AbstractValidator<Foo> {
    public FooValidator() {
        RuleFor(x => x.MainBar).SetValidator(new BarValidator());
        RuleFor(x => x.MainBar.BarNumber)
            .Cascade(CascadeMode.StopOnFirstFailure)
            .NotEmpty()
            .When(y => (!String.IsNullOrEmpty(y.AlternateBarOne.BarNumber)
                || !String.IsNullOrEmpty(y.AlternateBarTwo.BarNumber))).WithMessage("Bar required before 
                alternate bars.");
        // etc
    }
}

The problem is that the BarValidator happens for all of the Bar properties. In fact, even if I take out the rule for MainBar and don’t use the BarValidator at all, they’re still fired.

[JeremySkinner]

AssemblyScanner.FindValidatorsInAssemblyContaining<MyValidator>()
.Where(x => x.ValidatorType != typeof(BarValidator))
.ForEach(x => /* register as usual */)

[jawztherevenge]

Oy. Can it be achieved by making the validator implement PropertyValidator and IClientValidatable?