Rules are the smallest building blocks of a code review. Each code review applies different rules to assess the quality of a code base.
Rules form the basis of a code review. When you run a code review, rules are applied to a code base to see if the code adheres to them. You can modify supplied rules and create user-defined rules that are specific to your application design standards.
Rules that focus on similar functionality are in the same category. The previous sample rules are in the design principles category. Depending on the purpose of a code review, rules from various categories are applied.
Detailed information on a rule
You can get information about each rule, category, and code review in the Preferences window. For details, see the topic “Java preferences - Code Review page” for details.
Severity levels for rules
Although "recommendation" is the lowest severity level, do not discount how important it is to address these findings. They reflect a set of best practices and industry standards that engineering teams should adhere to. Even if these findings are not immediate problems, they could lead to problems in the future.
Rules that focus on similar functionality are in the same category. The previous sample rules are in the Design Principles category. Depending on the purpose of a code review, rules from various categories are applied.
Automated fixes for some rule findings
When a rule is not adhered to, the code review produces a finding. Some common findings come with a quick fix, which is a supplied automated solution. If a finding in the code review has a quick fix, it is indicated by one of the following icons:
Supplied rules
User-defined rules