-
Notifications
You must be signed in to change notification settings - Fork 465
Issues: dotnet/roslyn-analyzers
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Stack overflow in ServiceHub.RoslynCodeAnalysisService.exe
Bug
The product is not behaving according to its current intended design
DataFlow
help wanted
The issue is up-for-grabs, and can be claimed by commenting
CA1416 (Validate platform compatibility) doesn't work for implicit operators
Area-Microsoft.CodeAnalysis.NetAnalyzers
Bug
The product is not behaving according to its current intended design
False_Negative
No diagnostic is reported for a problematic case
help wanted
The issue is up-for-grabs, and can be claimed by commenting
#7350
opened Jul 11, 2024 by
LunarWhisper
Public API code fix unable to add APIs for compiler-defined members of record types
Area-CodeFix
Bug in code fixer
Bug
The product is not behaving according to its current intended design
#7237
opened Mar 8, 2024 by
chabiss
CA1848 false positive on The product is not behaving according to its current intended design
False_Positive
A diagnostic is reported for non-problematic case
help wanted
The issue is up-for-grabs, and can be claimed by commenting
LoggerMessage
methods
Area-Microsoft.CodeAnalysis.NetAnalyzers
Bug
#7150
opened Jan 17, 2024 by
TaffarelJr
CA1862 recommended for using string.Equals to perform case insensitive comparison but Entity Framework does not support it
Area-Microsoft.CodeAnalysis.NetAnalyzers
Bug
The product is not behaving according to its current intended design
False_Positive
A diagnostic is reported for non-problematic case
help wanted
The issue is up-for-grabs, and can be claimed by commenting
CA2000 false positive after upgrading to Visual Studio 2022 17.8
Area-Microsoft.CodeAnalysis.NetAnalyzers
Bug
The product is not behaving according to its current intended design
False_Positive
A diagnostic is reported for non-problematic case
help wanted
The issue is up-for-grabs, and can be claimed by commenting
CA1305 reports for nullable types cannot be disabled
Area-Microsoft.CodeAnalysis.NetAnalyzers
Bug
The product is not behaving according to its current intended design
help wanted
The issue is up-for-grabs, and can be claimed by commenting
CA1859 improperly handles default interface implementations
Area-Microsoft.CodeAnalysis.NetAnalyzers
Bug
The product is not behaving according to its current intended design
False_Positive
A diagnostic is reported for non-problematic case
help wanted
The issue is up-for-grabs, and can be claimed by commenting
CA1862 false positive with the same variable on both sides of the comparison
Area-Microsoft.CodeAnalysis.NetAnalyzers
Bug
The product is not behaving according to its current intended design
False_Positive
A diagnostic is reported for non-problematic case
help wanted
The issue is up-for-grabs, and can be claimed by commenting
Code metrics "lines of source code" incorrect
Area-CodeMetrics
Bug
The product is not behaving according to its current intended design
good first issue
help wanted
The issue is up-for-grabs, and can be claimed by commenting
CA1859: False positive in VB.NET iterator method
Area-Microsoft.CodeAnalysis.NetAnalyzers
Bug
The product is not behaving according to its current intended design
False_Positive
A diagnostic is reported for non-problematic case
CA1508 false positive: null check in finally block flagged when null assigned inside The product is not behaving according to its current intended design
DataFlow
False_Positive
A diagnostic is reported for non-problematic case
help wanted
The issue is up-for-grabs, and can be claimed by commenting
using
Area-Microsoft.CodeAnalysis.NetAnalyzers
Bug
CA1017: MarkAssembliesWithComVisible doesn't generate any diagnostic output
Area-Microsoft.CodeAnalysis.NetAnalyzers
Bug
The product is not behaving according to its current intended design
Need More Info
Priority:3
Nice to have (suitable for disabled by default rules and ported FxCop rules)
_LatestAnalysisLevel
should be package-dependent not SDK-dependent
Area-Infrastructure
Bug
CA1861: Avoid constant arrays improvements
Area-Microsoft.CodeAnalysis.NetAnalyzers
Bug
The product is not behaving according to its current intended design
False_Negative
No diagnostic is reported for a problematic case
needs-further-triage
#7001
opened Oct 21, 2023 by
Youssef1313
CA1058: False positive
Area-Microsoft.CodeAnalysis.NetAnalyzers
Bug
The product is not behaving according to its current intended design
False_Positive
A diagnostic is reported for non-problematic case
help wanted
The issue is up-for-grabs, and can be claimed by commenting
Setting <AnalysisMode<Category>> to Default doesn't work if <AnalysisMode> is All
Area-Microsoft.CodeAnalysis.NetAnalyzers
Bug
The product is not behaving according to its current intended design
#6987
opened Oct 17, 2023 by
jonathanou
CA1508
: Null check + assignment throw the analyzer off
Area-Microsoft.CodeAnalysis.NetAnalyzers
Bug
Microsoft.CodeAnalysis.ResxSourceGenerator emits compile errors when formatting argument names are C# keywords
Area-ResxSourceGenerator
Bug
The product is not behaving according to its current intended design
CA2000 false positive in VS 17.8.0 Preview 2
Area-Microsoft.CodeAnalysis.NetAnalyzers
Bug
The product is not behaving according to its current intended design
False_Positive
A diagnostic is reported for non-problematic case
help wanted
The issue is up-for-grabs, and can be claimed by commenting
Priority:3
Nice to have (suitable for disabled by default rules and ported FxCop rules)
ParameterNamesShouldMatchBaseDeclarationFixer gave me a an error.
Area-CodeFix
Bug in code fixer
Bug
The product is not behaving according to its current intended design
help wanted
The issue is up-for-grabs, and can be claimed by commenting
Reliability
Indicates a reliability issue (crash/data loss/test flakiness)
CA1508: False positive
Area-Microsoft.CodeAnalysis.NetAnalyzers
Bug
The product is not behaving according to its current intended design
False_Positive
A diagnostic is reported for non-problematic case
help wanted
The issue is up-for-grabs, and can be claimed by commenting
Assembly-level SupportedOSPlatform doesn't exclude other platforms/lower versions
Area-Microsoft.CodeAnalysis.NetAnalyzers
Bug
The product is not behaving according to its current intended design
CA1508 (Avoid dead conditional code) false positive
Area-Microsoft.CodeAnalysis.NetAnalyzers
Bug
The product is not behaving according to its current intended design
DataFlow
False_Positive
A diagnostic is reported for non-problematic case
help wanted
The issue is up-for-grabs, and can be claimed by commenting
.NET7.0: Suppress CA1416 when wrapped in UIDevice.CheckSystemVersion
Area-Microsoft.CodeAnalysis.NetAnalyzers
Bug
The product is not behaving according to its current intended design
Previous Next
ProTip!
Find all open issues with in progress development work with linked:pr.