hotfix: log expression when failing to analyze expression (#216) #13
Meir017
This run and associated checks have been archived and are scheduled for deletion.
Learn more about checks retention
Annotations
4 warnings
|
publish:
src/FluentAssertions.Analyzers/Tips/AsyncVoid.cs#L21
Enable analyzer release tracking for the analyzer project containing rule 'FluentAssertions0801' (https://github.com/dotnet/roslyn-analyzers/blob/main/src/Microsoft.CodeAnalysis.Analyzers/ReleaseTrackingAnalyzers.Help.md)
|
|
publish:
src/FluentAssertions.Analyzers/Tips/NullConditionalAssertionAnalyzer.cs#L18
Enable analyzer release tracking for the analyzer project containing rule 'FluentAssertions0800' (https://github.com/dotnet/roslyn-analyzers/blob/main/src/Microsoft.CodeAnalysis.Analyzers/ReleaseTrackingAnalyzers.Help.md)
|
|
publish:
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.
|
|
publish:
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
|