Conversion rules end up in the failure message multiple times

[dennisdoomen]

With configuration:
- Use declared types and members
- Compare enums by value
- Match member by name (or throw)
- Try conversion of all members. Try conversion of member x.SelectedMemberPath.Contains("Birthdate"). Try conversion of all members. 
- Be strict about the order of items in byte arrays
" does not.

[dennisdoomen]

Can't reproduce

[dennisdoomen]

The TryConversionStep is added every time a new instance of the SelfReferenceEquivalencyAssertionOptions is created. First when it copies over the UserEquivalencySteps from the defaults (which always adds the TryConversionStep as part of it), and possibly later

[krajek]

I will tackle the problem. Any comments before I start? Is there any test that reproduces the behaviour? Is it only about duplication in the description or the behaviour itself is also affected?

[dennisdoomen]

It's purely a cosmetic issue.

[jnyrup]

@krajek I guess this can be closed with #941 ?

[krajek]

Absolutely yes, thanks.

When I started #941 I was not sure it will solve the issue. As the PR developed over time fixes reached the root cause of the problem.