Skip to content

use single analyzer for fluentassertions tips - collections #30

use single analyzer for fluentassertions tips - collections

use single analyzer for fluentassertions tips - collections #30

Triggered via pull request December 12, 2023 06:07
Status Success
Total duration 1m 54s
Artifacts

benchmark.yml

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

Annotations

6 warnings
Performance regression check: src/FluentAssertions.Analyzers/Tips/Collections/FluentAssertionsOperationAnalyzer.cs#L18
The diagnostic message should not contain any line return character nor any leading or trailing whitespaces and should either be a single sentence without a trailing period or a multi-sentences with a trailing period
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