-
Notifications
You must be signed in to change notification settings - Fork 509
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
Implement new diagnostic SA1652 (EnableXmlDocumentationOutput) #1055
Conversation
{ | ||
if (context.Tree.Options.DocumentationMode == DocumentationMode.None) | ||
{ | ||
context.ReportDiagnostic(Diagnostic.Create(Descriptor, context.Tree.GetLocation(new TextSpan(0, 0)))); |
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.
Do we really want to report a diagnostic on every SyntaxTree?
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.
Maybe, maybe not. Since the documentation mode is a property of each SyntaxTree
, I figured this makes sense at least until someone has a major problem with it.
a6602b0
to
886f05d
Compare
886f05d
to
965be0e
Compare
{ | ||
return; | ||
} | ||
|
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.
No way to avoid the repetition of these?
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.
Not without additional refactoring. Each of these methods is its own entry and exit point for analysis of a particular type of syntax node.
👍 |
Implement new diagnostic SA1652 (EnableXmlDocumentationOutput)
Fixes #1053.