Artur Krajewski

@lg2de hey, coincidentally I had the same issue a few days ago and asked on the slack channel. After a short discussion, we ended up with initial idea of `ThrowingOnUnexpectedMembers`...

I was talking about preparing a PR fast and I gave it a shot. Unfortunately, preparing `ThrowingOnUnexpectedMembers` is not that easy, because of the code (` IEquivalencyAssertionOptions`, `StructuralEqualityEquivalencyStep`, `IMemberMatchingRule` and...

@cbries could you describe your use case in detail, please? Do you want to register some code to be run for any failed test? Are you sure that test frameworks...

@jaslam94 https://github.com/destructurama and ByIgnoring project I guess would be a start point. You could also write one yourself, it seems it would not be much more than: ``` logEvent.RemovePropertyIfPresent("StackTrace"); ```...

@jaslam94 also https://newbedev.com/how-to-remove-properties-from-log-entries-in-asp-net-core

@jaslam94 I haven't tried it, but wouldn't that be enough to remove the `Exception` and keep just the `ExceptionDetails.StackTrace`? ``` logEvent.RemovePropertyIfPresent("Exception"); ```

@jaslam94 you are right, thanks for the explanation. I have recalled that we had a similar discussion a long time ago and that is why we decided to omit `StackTrace`...

@kmcclellan Thanks for reaching out. Let me understand your case better. Correct me if I am wrong, please. You have some custom exceptions for which you intentionally would like to...

Just a question: is it worth it? The cost of reflection is negligible and paid just for the first time exception is destructured. The cost is also minuscule compared to...

From a quick look, it may be the case that we actually handle duplicate names incorrectly in this scenario. Thanks for the report I will try to take a look...