CollectionShouldNotContainProperty is too aggresive about fluentassertions.analyzers HOT 2 CLOSED

@jnyrup since the case of a Should followed by OnlyContain does'n currently have a codefix maybe I should just ignore this case for now untill I fix #2

In this case the CodeFix should be

list.Should().NotContain(e => !e.Contains(""));

which seems fair

from fluentassertions.analyzers.

Maybe I was too quick on this one.
I personally prefer OnlyContain(e => e.MyBooleanProperty) over NotContain(e => !e.MyBooleanProperty) and that's the example in https://fluentassertions.com/tips#Collections-22.

But if someone prefers it the other way around, it is of course beneficial to have a tools to do the transforms.
For many of its refactorings, Roslynator has methods for transforming in both directions, but has one disabled by default.
E.g.
https://github.com/JosefPihrt/Roslynator/blob/master/docs/refactorings/RR0168.md
and
https://github.com/JosefPihrt/Roslynator/blob/master/docs/refactorings/RR0171.md

from fluentassertions.analyzers.