Describe the solution you'd like
Take a look at the following code example:
See those dots under the "ex" in expectations? That's IDE0058, which is giving us a hint that we shouldn't ignore the return value. But fluent APIs are all about ignoring return values :). So it might be nice for Rocks to detect when the following diagnostics are created with respect to an adornments fluent API invocation:
Basically, if an adornments return value is ignored and one of the diagnostics in the list is created, suppress it.
Describe the solution you'd like
Take a look at the following code example:
See those dots under the "ex" in
expectations? That'sIDE0058, which is giving us a hint that we shouldn't ignore the return value. But fluent APIs are all about ignoring return values :). So it might be nice for Rocks to detect when the following diagnostics are created with respect to an adornments fluent API invocation:Basically, if an adornments return value is ignored and one of the diagnostics in the list is created, suppress it.