When for example two objects reference each other over properties and FluentAssertions wants to build an error message then the DefaultValueFormatter causes a StackoverflowException because it loops endlessly over the properties from one object to the other and back and forth ...
See attachment for a sample reproducing the problem.
It would be nice if FluentAssertions could detect cycles, but maybe it is simple enough to somehow prevent the error message to be built or limit it to a certain depth (could even be hard-coded I think - error message would be too long anyway).
See attachment for a sample reproducing the problem.
It would be nice if FluentAssertions could detect cycles, but maybe it is simple enough to somehow prevent the error message to be built or limit it to a certain depth (could even be hard-coded I think - error message would be too long anyway).