-
Type: New Feature
-
Status: Open
-
Priority: Minor
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Core Dev Guide (CORG)
-
Tags:
Describe the recommended tools and workflows about making use of SonarQube analysis during the development.
https://doc.nuxeo.com/corg/secure-coding/
https://doc.nuxeo.com/corg/code-quality-with-ide-plugins/
For instance, Antoine Taillefer is now used to:
- use Eclipse plugin https://www.sonarlint.org/eclipse/ , looking at the blue markers on the right of the editor and the "SonarLint On-The-Fly" and "SonarLint Report" views
- remove all immediate and without side effect issues, ie everything but "reduce method's complexity", "too many inheritance", "TODO"...
- when the rule is not clear, he checks the "SonarLint Rule" view
- optionally looking at the online UI for a better understanding, using the filters on the left, based on rule ID.