Just started using your library and so far I find it excellent. One thing though: I use it for comparing NHibernate objects and sometimes I have objects with bi-directional references. The assertions fails and states that a cyclic reference was detected. Could it be possible though to configure that instead of throwing an exception on a cyclic reference that it should rather just not follow that reference and still complete the rest of the comparison successfully?
Comments: ** Comment from web user: dennisdoomen **
Comments: ** Comment from web user: dennisdoomen **
I think we misunderstood the requirement. It should be configurable (through the fluent API). By default it should still throw, but by including a fluent property or method you can instruct it to ignore it for a particular assertion. The current change is breaking the existing behavior.