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
SonarQube 8.5 classifies grvy:org.codenarc.rule.naming.VariableNameRule.fixed as a "Bug" whereas I argue that it should be classified as a "Code smell".
From the official documentation:
Bug | An issue that represents something wrong in the code. If this has not broken yet, it will, and probably at the worst possible moment. This needs to be fixed. Yesterday.
Code Smell | A maintainability-related issue in the code. Leaving it as-is means that at best maintainers will have a harder time than they should making changes to the code. At worst, they'll be so confused by the state of the code that they'll introduce additional errors as they make changes.
Verifies that the name of each variable matches a regular expression. By default it checks that non-final variable names start with a lowercase letter and contains only letters or numbers. By default, final variable names start with an uppercase letter and contain only uppercase letters, numbers and underscores.
Hi,
SonarQube 8.5 classifies grvy:org.codenarc.rule.naming.VariableNameRule.fixed as a "Bug" whereas I argue that it should be classified as a "Code smell".
From the official documentation:
Source: https://docs.sonarqube.org/latest/user-guide/concepts/
"Variable Name" (grvy:org.codenarc.rule.naming.VariableNameRule.fixed) rule description:
Versions:
Related: #14
The text was updated successfully, but these errors were encountered: