2

In the previous versions of Fluent Assertions, there was a possibility to compare two collections with different members types and names by creating a class which implements IEquivalencyStep: https://stackoverflow.com/a/55898570

Unfortunately, version 6 changed this interface and the trick does not work. Is there any workaround for this kind of comparison in the current version of Fluent Assertions?

rgb
  • 1,750
  • 1
  • 20
  • 35

1 Answers1

0

Why do you think this "trick" doesn't work anymore?

Also good to know that we're working on first-class support for comparing different properties.

Dennis Doomen
  • 8,368
  • 1
  • 32
  • 44
  • Interface IEquivalencyStep was changed: method CanHandle does not exist and method Handle has different signature. – rgb Dec 01 '21 at 09:04