Skip to content

introduce single CollectionAnalyzer for collection assertions #25

introduce single CollectionAnalyzer for collection assertions

introduce single CollectionAnalyzer for collection assertions #25

Triggered via pull request December 10, 2023 05:42
Status Success
Total duration 1m 53s
Artifacts

benchmark.yml

on: pull_request
Performance regression check
1m 44s
Performance regression check
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
Performance regression check: src/FluentAssertions.Analyzers/Tips/Collections/CollectionShouldNotBeNullOrEmpty.cs#L15
'CollectionShouldNotBeNullOrEmptyAnalyzer.DiagnosticId' hides inherited member 'CollectionAnalyzer.DiagnosticId'. Use the new keyword if hiding was intended.
Performance regression check: src/FluentAssertions.Analyzers/Tips/Collections/CollectionShouldNotBeNullOrEmpty.cs#L18
'CollectionShouldNotBeNullOrEmptyAnalyzer.Message' hides inherited member 'CollectionAnalyzer.Message'. Use the new keyword if hiding was intended.
Performance regression check: 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.
Performance regression check: src/FluentAssertions.Analyzers/Utilities/FluentAssertionsCodeFixProvider.cs#L28
Provide an explicit argument for optional parameter 'equivalenceKey', which is non-null and unique for each kind of code action created by this fixer