[Development] Sonarqube default quality profile has changed

[brrritssocold]

The default quality profile for Flex has been updated ("Sonar way"). This deactivated some rules, resulting in a lot less issues getting reported.

This could be an opportunity to create a Quality profile for CoC that matches the Coding guidelines.

Thoughts?

[Stadler76]

The default quality profile for Flex has been updated ("Sonar way"). This deactivated some rules, resulting in a lot less issues getting reported.

Could you be more specific about what has actually been changed?

This could be an opportunity to create a Quality profile for CoC that matches the Coding guidelines.

Thoughts?

Sounds good, but we shouldn't enforce all parts of the guideline since I see that more as a recommendation for better readability and more consistent code style and less as a must do.

To get to the point: I think setting a soft cap and a hard cap for line length could be a good start, if that is possible.

[brrritssocold]

Could you be more specific about what has actually been changed?

Sure. I cannot find a change log for the default quality profiles (very annoying), so from memory these rules were deactivated:

• "===" and "!==" should be used instead of "==" and "!="
• "switch case" clauses should not have too many lines of code
• "switch" statements should not be nested
• Functions should not contain too many return statements
• Statements should be on separate lines
• Statements should end with semicolons

Source: current quality profile

To get to the point: I think setting a soft cap and a hard cap for line length could be a good start, if that is possible.

I did a quick search, it is does not seem possible to add or modify rules in the 'Community edition' of Sonarqube / Sonarcloud.