Help or NFR: Better way to deactivate rules that are active in SonarWay profiles

[Colin]

@andrew-garland

However, I don’t share the mindset that the particular rules that happen to be in the SonarWay profile must be considered the minimal accepted set as a quality baseline.

I don’t either. I only meant that in general, this was the use-case considered for inheritance of Quality Profiles (minimum baseline, whatever it is, + more)

@andrew-garland

Stated another way: I consider the SonarWay quality profiles to be the community/industry “best practice” guidelines.

It’s an interesting percecption we’re kind of aware of – but doesn’t reflect exactly what this Quality Profile was born to represent. It’s meant to represent non-controversial rules with few false-positives to get started using our products. From the docs…

The Sonar way Quality Profiles are a good starting-point as you begin analyzing code, and they start out as the default Quality Profiles for each language. That being said, we recommend that you Copy this profile and begin to fine-tune the contents. Why?

• Default Quality Profiles are not editable, so you won’t be able to customize the Sonar way to your needs
• The Sonar way becomes a baseline against which you can track your own Quality Profiles
• The Sonar way may be updated over time to adjust which rules are included and adjust rule severities.

@andrew-garland

The design today already allows an organization to edit inherited rules to make them less effective (e.g. change something to an Info level), so it seems there is already a tacit acknowledgement that not every rule in the SonarWay profile is appropriate for all codebases.

A fair point.

Thanks for the feedback.