Bug for NullConditionalAssertion about fluentassertions.analyzers HOT 4 CLOSED

Just noticed the same thing. This is definitely a false positive.

from fluentassertions.analyzers.

Please fix.

In an expression like:

X?.Y.Should().Be(expected);

it is absolutely true that the entire "chain" .Y.Should().Be(expected) will be skipped if X is null. In particular, Should and Be are never called, and a warning is reasonable.

However, in the statement:

(X?.Y).Should().Be(expected);

the chain stops at ) and Should is always called. It is an extension method that can be called in a meaningful way on a null, even a reference-type null (which can occur if the compile-time type of Y is a reference type; in iron9light's example it was a value type which gives a Nullable<> which is also fine).

from fluentassertions.analyzers.

@JeppeSN which analyzer is triggering the warning here?

from fluentassertions.analyzers.

resolved by #170

from fluentassertions.analyzers.