You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
I just started to use your great plugin to review my code, however i just encountered an issue that think would be nice to fix.
Description
The cognitive complexity rule "Cognitive Complexity of methods should not be too high" trigger issues, but do not increase technical debt. There is not remediation cost formula associated with the rule.
Repro steps
Step A
Activate the "Cognitive Complexity of methods should not be too high" rule if necessary.
Create a complex method ( or lower the rule threshold ) in order to create a violation in a code sample.
Step B
Analyse it. And you'll see an issue, but no increase of the technical debt in the SonarQube App
Expected behavior
There should be an effort associated with the issue
Actual behavior
No cost increase.
Known workarounds
None
Related information
SonarC# Version6.7.1 (build 4347)
SonarQube Scanner for MSBuild 4.0
Microsoft (R) Build Engine version 15.5.180.51428
Thanks for your work.
Regards
Eric A
The text was updated successfully, but these errors were encountered:
Hi @Errrric, thanks for the feedback, we will fix this in the next release of SonarC# in a few weeks. The fix will not be perfect though, because for technical reasons SonarC# supports only Constant remediation functions. I override the function in RSPEC to Constant/10min (it could vary depending on the complexity, but that's what the other functions are).
valhristov
changed the title
Cognitive Complexity issues do not increase technical debt
Update S3776: "Cognitive Complexity" should provide values for remediation function and cost
Jan 26, 2018
Hello,
I just started to use your great plugin to review my code, however i just encountered an issue that think would be nice to fix.
Description
The cognitive complexity rule "Cognitive Complexity of methods should not be too high" trigger issues, but do not increase technical debt. There is not remediation cost formula associated with the rule.
Repro steps
Step A
Activate the "Cognitive Complexity of methods should not be too high" rule if necessary.
Create a complex method ( or lower the rule threshold ) in order to create a violation in a code sample.
Step B
Analyse it. And you'll see an issue, but no increase of the technical debt in the SonarQube App
Expected behavior
There should be an effort associated with the issue
Actual behavior
No cost increase.
Known workarounds
None
Related information
SonarC# Version6.7.1 (build 4347)
SonarQube Scanner for MSBuild 4.0
Microsoft (R) Build Engine version 15.5.180.51428
Thanks for your work.
Regards
Eric A
The text was updated successfully, but these errors were encountered: