AsImplementedInterfaces() registering too much

I understand that AsImplementedInterfaces() registers all implemented interfaces, however this is sometimes too much. Take for instance, the FluentValidation library, you may scan with the following:

.AddClasses(c => c.AssignableTo(typeof(IValidator<>))).AsImplementedInterfaces()

This will pickup all the AbstractValidator<T> implementations you have, but this class implements the following interfaces:

IValidator<T>
IEnumerable
IEnumerable<IValidationRule>
IValidator

Which means you get entries for all of these, not just the desired IValidator<T> and I need to do the following to get rid of the superfluous entries:

services.RemoveAll<IValidator>();
services.RemoveAll<IEnumerable>();
services.RemoveAll<IEnumerable<IValidationRule>>();

Is there any way to do this without having to remove the extra entries afterwards?

[khellang]

I’ve added an overload to AsImplementedInterfaces that lets you filter the interfaces you’d like to register using a predicate and pushed it to NuGet as part of v4.1.0 😄 I’ll leave the issue open to track the breaking change of filtering out some common types by default,

[khellang]

I do not actually need to register IRegisteredObject but it also seems like there is no way to tell Scrutor to ignore this interface.

@THammond9 There is. It’s mentioned as a workaround in this issue.

I think a short-term non-breaking fix for this issue would be to introduce an overload of AsImplementedInterfaces that takes a filter predicate so people could filter out what they don’t want.

If anyone wants to send a PR before I get to it, that would be cool 😎