Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Rule S110: "filteredClasses" documentation should describe which delimiter to use or provide specific examples #519

Closed
RalfKoban opened this issue Jul 1, 2017 · 1 comment
Closed

Rule S110: "filteredClasses" documentation should describe which delimiter to use or provide specific examples #519

RalfKoban opened this issue Jul 1, 2017 · 1 comment
Assignees
@Evangelink
Milestone
6.2

Comments

@RalfKoban
Copy link

Hi,

The rule S110 "Avoid excessive inheritance provides a parameter called "filteredClasses" (http://www.sonarlint.org/visualstudio/rules/index.html#version=6.0.0.2033&ruleId=S110).

The description for that parameter should list the delimiter to use in case someone wants to provide some filters. In addition it should be mentioned whether those strings are only the class names or shall be the full names incl. the namespaces.

  • SonarC# Version: 6.0.0.2033
  • Visual Studio Version: Irrelevant - it's about documentation
  • If running through the Scanner for MSBuild, its version: Irrelevant - it's about documentation

Best regards,
Ralf Koban
@RalfKoban RalfKoban changed the title S110 "filteredClasses" documentation should describe which delimiter to use or provide specific examples Rule: S110 "filteredClasses" documentation should describe which delimiter to use or provide specific examples Jul 1, 2017
@RalfKoban RalfKoban changed the title Rule: S110 "filteredClasses" documentation should describe which delimiter to use or provide specific examples Rule S110: "filteredClasses" documentation should describe which delimiter to use or provide specific examples Jul 1, 2017
@Evangelink Evangelink added this to the 6.2 milestone Jul 2, 2017
@Evangelink
Copy link
Contributor

Evangelink commented Jul 2, 2017 •
edited
Loading

Hi @RalfKoban,

Thanks for the feedback. We will make sure to update the documentation for the 6.2 release.

RSPEC-110

@Evangelink Evangelink mentioned this issue Jul 7, 2017
Merged
@valhristov valhristov assigned Evangelink and unassigned valhristov Jul 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Evangelink Evangelink

Labels
None yet
Projects
None yet
Milestone
6.2
Development

No branches or pull requests
3 participants
@RalfKoban @Evangelink @valhristov