Ambiguous invocation when using BeEquivalentTo with Excluding with <6.0

This code brings compiler exception “ambiguous invocation” when using 6.0.0 version, but works with lower versions.

private class Test1
{
    public string Name { get; set; }
}

private class Test2
{
    public string Name { get; set; }
}

[Fact]
public async Task Test_Case()
{
    var test1 = new Test1();
    var test2 = new Test2();

    //Work around
    //Expression<Func<IMemberInfo, bool>> expression = info => info.Name == "Level.Level.Text";
    //test1.Should().BeEquivalentTo(test2, opts => opts.Excluding(expression));

    test1.Should().BeEquivalentTo(test2,
        opts => opts.Excluding(ctx => ctx.SelectedMemberPath == "Level.Level.Text"));
}

[ajeckmans]

SelectedMemberPath was renamed to Path. So test1.Should().BeEquivalentTo(test2, opts => opts.Excluding(ctx => ctx.Path == "Level.Level.Text")); should work.

The docs unfortunately do not reflect this yet. Nor was it mentioned as a breaking change in the release notes.

[ajeckmans]

@dennisdoomen There is also the issue of the docs all mentioning the “old” way and not the new. Is there a guideline on how to write the documentation? (I think only https://github.com/fluentassertions/fluentassertions/blob/master/docs/_pages/objectgraphs.md mentions it)