-
Notifications
You must be signed in to change notification settings - Fork 470
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
Remaining work for Security analyzers to respect excluded_symbol_names
option
#2706
Comments
Would be good to also take care of #2687 (comment) |
Thanks @Evangelink for the ping. Still need to figure out what the behavior should be and implement that, if needed. |
Except if I am missing something here but the ticket and the comment are talking about the |
It's currently handled by skipping dataflow analysis when both rules disable a symbol. This issue was opened to figure out what to do if one rule disables the symbol for dataflow analysis, and the other rule leaves the symbol enabled for dataflow analysis. I suppose I can say no one's complained so far, so the current implementation is good enough. 😄 |
Ohhh got it! I saw the TODO in the code but I thought this was one TODO missing an associated work item. My bad! |
Would it be possible to say that we store the result of the foreach (KeyValuePair<(Location Location, IMethodSymbol? Method), HazardousUsageEvaluationResult> kvp
in allResults)
{
DiagnosticDescriptor descriptor;
switch (kvp.Value)
{
case HazardousUsageEvaluationResult.Flagged:
if (skipDefinitelyInsecureSerializer)
{
continue;
}
else
{
descriptor = DefinitelyInsecureSerializer;
}
break;
case HazardousUsageEvaluationResult.MaybeFlagged:
if (skipMaybeInsecureSerializer)
{
continue;
}
else
{
descriptor = MaybeInsecureSerializer;
}
break;
default:
Debug.Fail($"Unhandled result value {kvp.Value}");
continue;
}
compilationAnalysisContext.ReportDiagnostic(
Diagnostic.Create(
descriptor,
kvp.Key.Location));
} WDYT? |
See #2699 (comment).
The text was updated successfully, but these errors were encountered: