Jonas Nyrup

I don't think `ContainOnlyEquivalentOf` is the best name. To me that name implies that this snippet would pass. ```cs "reD RED ReD".Should().ContainOnlyEquivalentOf("red"); ``` How about `ContainEquivalentOfAll` and `ContainEquivalentOfAny`.

I think we need to compare some pros/cons and other options before adding a `StringComparison` parameter. Generally we have tried to "limit" the provided assertions to more general use cases,...

A *complete minimal example* would be ```csharp // Act Action act = () => throw new Exception(); // Assert act.Should().Throw().Which.Message.Should().Be("Value"); ``` > Message: Expected act to be "Value" with a...

Please open a new issue where we can discuss only the APIs. Separating API review from implementation API is less time-consuming for us, and hopefully also for you. I'm writing...

@jmg48 The .NET community is somewhat split these days on whether async methods _can_, _should_ or _must_ be suffixed with `Async`. In my own tests these days, I tend to...

I've tried poking around with this and even through I set a stack trace on the exception with reflection, it seems the `throw` keyword overwrites it again. Another approach could...

> If that works on all platforms, then I would also remove the `AssertionScope.FailWith` There should be nothing platform specific about catching an exception and throwing the catched exception. I...

Except for debugging into FA I don't see any case, that's why I'm asking :)

To support this, we could e.g. to take an `IEqualityComparer` as parameter to compare elements for equality. I.e. introduce the following methods in the API: ```csharp Equal(IEnumerable other, IEqualityComparer comparer,...

@james-ecargo @AroglDarthu Fluent Assertions is a spare time project, heavily driven by user contributions. Unless an issue/PR is explicitly marked with a [milestone](https://github.com/fluentassertions/fluentassertions/milestones), there are no promises about if/when a...