-
Notifications
You must be signed in to change notification settings - Fork 231
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
ReportIssue: Remove obsolete overloads from SonarAnalysisContextExtensions #9356
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
{ | ||
cc.ReportIssue(diagnostic); | ||
} | ||
ReportUnusedPrivateMembers(cc, usageCollector, removableInternalTypes, SyntaxConstants.Internal, new()); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unrelated but important. We report in CompilationEnd and as such we should add the CompilationEnd tag to the diagnostic desscriptor. Otherwise we do violate RS1037
If we fail to do so, some IDE scenarios are broken and issues appear and disappear in the IDE error list. See
dotnet/roslyn-analyzers#6282 for more links to more details about the issue. We do have several such violations in our code base. See also #8437
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Our DescriptorFactory
doesn't have a parameter to accept this, so I can't do anything in this PR.
bcd7733
to
fad8aef
Compare
Quality Gate passed for 'Sonar .NET Java Plugin'Issues Measures |
Quality Gate passed for 'SonarAnalyzer for .NET'Issues Measures |
Follow up of #9298 effort
This PR:
SonarAnalysisContextExtensions
extensionsSonarCompilationReportingContext
andSonarSymbolReportingContext
separately