Description

I am comparing objects that inherit from a base class from a library assembly that I don't control. That base class implements properties of an internal interface explicitly. Since #2794 / 6.12.2 these explicitly implemented properties are now compared.

This is problematic because

1. I cannot exclude these properties using .Excluding (or .For(..).Exclude(..)) because I cannot name the property. I cannot name the property because I cannot name the interface (it's internal).
2. IncludingAllDeclaredProperties doesn't seem to have an effect. Contrary to what the doc comment on the method says, the explicitly implemented property of the internal interface seems to be treated as a public property declared on my type. Sure, interface implementations are technically public, but I would expect the visibility of the interface to "win" here.

Reproduction Steps

// Assembly A (not under my control)
internal interface IEntity {
  bool IsValid { get; }
}

public class Base(bool v) : IEntity {
  bool IEntity.IsValid { get ; } = v;
}

// Assembly B (my assembly)
// references assembly A
class MyClass(bool v) : Base(v) {
}

// Objects should be equivalent because internal interfaces are ignored.
new MyClass(true).Should().BeEquivalentTo(new MyClass(false));

Expected behavior

Internal interfaces are ignored for BeEquivalentTo.

Actual behavior

Explicit property implementations of internal interfaces are considered for BeEquivalentTo.

Regression?

This worked as expected in 6.12.1. It is broken in 6.12.2.

Known Workarounds

Use the IMemberInfo overload of .Excluding.

Configuration

.NET 8

Other information

No response

Are you willing to help with a pull-request?

No