docs: fluent assertions string assertions (#396) #682
Annotations
12 warnings
src/FluentAssertions.Analyzers/Tips/NunitCodeFixProvider.cs#L674
Parameter 'constraint' is unread.
|
src/FluentAssertions.Analyzers/Tips/AsyncVoid.cs#L74
'AsyncVoidCodeFix' registers one or more code fixes, but does not override the method 'CodeFixProvider.GetFixAllProvider'. Override this method and provide a non-null FixAllProvider for FixAll support, potentially 'WellKnownFixAllProviders.BatchFixer', or 'null' to explicitly disable FixAll support.
|
src/FluentAssertions.Analyzers/Tips/NunitCodeFixProvider.cs#L674
Parameter 'constraint' is unread.
|
src/FluentAssertions.Analyzers/Tips/AsyncVoid.cs#L74
'AsyncVoidCodeFix' registers one or more code fixes, but does not override the method 'CodeFixProvider.GetFixAllProvider'. Override this method and provide a non-null FixAllProvider for FixAll support, potentially 'WellKnownFixAllProviders.BatchFixer', or 'null' to explicitly disable FixAll support.
|
src/FluentAssertions.Analyzers.FluentAssertionAnalyzerDocs.Nunit3/Nunit3AnalyzerTests.cs#L274
Consider using the constraint model, Assert.That(...), instead of the classic model, CollectionAssert(...) (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2049.md)
|
src/FluentAssertions.Analyzers.FluentAssertionAnalyzerDocs.Nunit3/Nunit3AnalyzerTests.cs#L327
Consider using the constraint model, Assert.That(...), instead of the classic model, CollectionAssert(...) (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2049.md)
|
src/FluentAssertions.Analyzers.FluentAssertionAnalyzerDocs.Nunit3/Nunit3AnalyzerTests.cs#L351
Consider using the constraint model, Assert.That(...), instead of the classic model, CollectionAssert(...) (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2049.md)
|
src/FluentAssertions.Analyzers.FluentAssertionAnalyzerDocs.Nunit3/Nunit3AnalyzerTests.cs#L404
Consider using the constraint model, Assert.That(...), instead of the classic model, CollectionAssert(...) (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2049.md)
|
src/FluentAssertions.Analyzers.FluentAssertionAnalyzerDocs.Nunit3/Nunit3AnalyzerTests.cs#L513
Consider using the constraint model, Assert.That(actual, Is.SameAs(expected)), instead of the classic model, ClassicAssert.AreSame(expected, actual) (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2015.md)
|
src/FluentAssertions.Analyzers.FluentAssertionAnalyzerDocs.Nunit3/Nunit3AnalyzerTests.cs#L527
Consider using the constraint model, Assert.That(actual, Is.SameAs(expected)), instead of the classic model, ClassicAssert.AreSame(expected, actual) (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2015.md)
|
src/FluentAssertions.Analyzers.FluentAssertionAnalyzerDocs.Nunit3/Nunit3AnalyzerTests.cs#L563
Consider using the constraint model, Assert.That(actual, Is.Not.SameAs(expected)), instead of the classic model, ClassicAssert.AreNotSame(expected, actual) (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2031.md)
|
src/FluentAssertions.Analyzers.FluentAssertionAnalyzerDocs.Nunit3/Nunit3AnalyzerTests.cs#L783
Consider using the constraint model, Assert.That(...), instead of the classic model, CollectionAssert(...) (https://github.com/nunit/nunit.analyzers/tree/master/documentation/NUnit2049.md)
|
This job succeeded
Loading