26 lines
904 B
Plaintext
26 lines
904 B
Plaintext
=== On 2015-11-24T14:01:46Z Ann Campbell Wrote:
|
|
\[~tamas.vajk] see truncated description in main task.
|
|
|
|
=== On 2015-11-24T14:27:15Z Tamas Vajk Wrote:
|
|
\[~ann.campbell.2] It seems okay.
|
|
|
|
|
|
Do we mark somehow rules that are library dependent? For example, out of the box we only have ``++Assert.IsTrue++`` and ``++Assert.AreEqual++``-like assertions. With those, this rule doesn't make sense. But when you add a library like "FluentAssertions", you could write "something.Should();" instead of "something.Should().NotBeNull()".
|
|
|
|
=== On 2015-11-24T14:36:37Z Ann Campbell Wrote:
|
|
\[~tamas.vajk] should we expand the examples to include:
|
|
|
|
----
|
|
Assert; // Noncompliant
|
|
----
|
|
|
|
----
|
|
Assert.AreNotSame(actual,"");
|
|
----
|
|
? Does the noncompliant version compile?
|
|
|
|
=== On 2015-11-24T14:49:24Z Tamas Vajk Wrote:
|
|
\[~ann.campbell.2] No, ``++Assert;++`` on its own doesn't compile.
|
|
|
|
include::../comments-and-links.adoc[]
|