-
Notifications
You must be signed in to change notification settings - Fork 508
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
Proposal: Allow fine-grained control over when documentation is checked on interfaces #3100
Comments
I'm 👍 on this, with the one change that we use |
Is there a known state for this feature? |
Based on this method, I'm not sure a change is needed here. Line 60 in f5f4ca9
The following should be equivalent to the new
|
This would require documentation on all exposed types, not just interfaces. |
if you don't want docs on other types that are public make them internal and use |
Thanks @bjornhellander missed that case. |
Spawned from #2934 (comment)
Overview
This is a proposal to allow control over how much StyleCop cares about documentation on internal interfaces.
Background
According to the above issue,
documentInterfaces=true
takes precedence overdocumentInternalElements = false
. This means that if you want StyleCop to check documentation on public interfaces, it will also check documentation on internal interfaces. There is currently no way to have StyleCop check documentation on public interfaces while ignoring internal interfaces.Rationale
We have many external interfaces and each must have documentation that adheres to all the StyleCop rules. However, for internal interfaces (of which we also have many), we don't care if any of the documentation elements are missing.
Suggested Solution
I propose that the
documentInterfaces
item instylecop.json
be enhanced to support the following values:"all"
- (default value) Indicates that documentation on internal as well as public interfaces should be checked."external"
- Indicates that documentation should only be checked on interfaces if they are externally visible."none"
- Indicates that documentation should not be checked on interfaces (equivalent to"documentInterfaces": false
in current behaviour).true
- For backward compatibility. Equivalent to"all"
false
- For backward compatibility. Equivalent to"none"
Example:
The text was updated successfully, but these errors were encountered: