Jonas Nyrup

@Evangelink No need to apologize. There are some examples in the [docs](https://fluentassertions.com/typesandmethods/). At work I've used the type assertion API, as a poor man's code analyzer, to avoid some coding...

@chvollm I had a look at it and saw that I hadn't updated this with the contributions from #1306. Did you spot more?

The ones in #1700 are for `MethodInfoSelectorAssertions`. `MethodInfoSelector` is another class used to filter methods. E.g. ```cs typeof(MyType) .Methods() //

> @jnyrup Is there an ordered list of top 10 requests? For the APIs from this issue? No. I would probably go with what brings most consistency across all type...

`PropertyPath` was removed from `ISubjectInfo` in [v4](https://github.com/fluentassertions/fluentassertions/releases/tag/4.0.0). Use `SelectedMemberPath` instead ```csharp clientDtos.ShouldBeEquivalentTo(clientDtosToCompare, option => option .Excluding(x => x.SelectedMemberPath.EndsWith("ClientName"))); ```

@davisnw Can you provide a complete example? Or just mention which *specific* overload of `BeEquivalentTo` you are using? If you use a generic overload of `BeEquivalentTo`, i.e. one where the...

While the output looks good, introducing a blocking call would go against our statement of "fully embrace asynchronous code". > One of them is the way we supported async code....

Are there other pieces of information in the `HttpResponseMessage` that would be valuable to include in the failure message that doesn't need an async/blocking call?

> A separate package already exists at https://github.com/balanikas/FluentAssertions.Http. Makes me wonder why this was integrated. `FluentAssertions.Http` had it's last update three years ago. I haven't checked if it even works...

Btw, I'm AFK for a week from today. I'll continue reviewing once I'm back.