Codiga provides multiple sets of rules for 12+ languages. Below we provide a link and a description for all the rules supported by our platform. Note that not all the rules are being listed and described below.
Function nested too deeply.
Function has 3 return statements which exceeds the limit of 2.
In most cases using a spread operator causes a full copy of the array to be created before calling a method which has a very high performance penalty.
Too many throw statements in function.
Top level constant names should match the pattern: [A-Z][\_A-Z0-9]*
An abstract class without a concrete member can be refactored to an interface.
Reports empty init expressions. Empty blocks of code serve no purpose and should be removed.
Function parameter is unused
Instead of simply printing a stacktrace a better logging solution should be used.
Equals methods should always report if some other object is equal to the current object