Skip to content

Commit b3ce71a

Browse files
Update rules/Proj0039.md
Co-authored-by: Gemberkoekje <[email protected]>
1 parent 03d4ecc commit b3ce71a

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

rules/Proj0039.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ Some extensions in Visual Studio (like VS Spell Checker or SonarQube IDE) add wa
3030
## 6. False positives
3131
Although analyser rule builders – like us – try their best to come up with robust and correct analysers, it turns out that now and then a rule reports a false positive. In such cases it is better to not to have to supress the issue, or to adjust the code just so satisfy the rule, but to file a bug report and wait for an update that fixes the FP.
3232

33-
In the end, warnings are an indication as technical debt, and should be handled a such: with care. Using tools like Qodana and SonarQube can create reports on pull requests to reduce the introduction of new warnings (ideally to zero).
33+
In the end, warnings are an indication of technical debt, and should be handled a such: with care. Using tools like Qodana and SonarQube can create reports on pull requests to reduce the introduction of new warnings (ideally to zero).
3434

3535
On a regular basis the team working on the project should allocate time to address outstanding issues that should be fixed, or decide that a certain rule is not worth the effort for the project. The goal should be to get as close to zero warnings as possible.
3636

0 commit comments

Comments
 (0)