facebook pixelCodiga Analysis Java Rules, category best practice
BACK TO LIST

Java rules

The Codiga Code Analysis engine supports hundreds of rules for Java, checking that your code is safe and secure. Start using Codiga today to check your code and automate your code reviews to find issues in every pull request and merge with confidence.

AbstractClassWithoutAbstractMethod

Best practice
Warning

This abstract class does not have any abstract methods

Learn more

AvoidReassigningParameters

Best practice
Error

Avoid reassigning parameters

AvoidUsingHardCodedIP

Best practice
Warning

Do not hard code the IP address

CheckResultSet

Best practice
Warning

Always check the return of one of the navigation method (next

ConstantsInInterface

Best practice
Warning

Avoid constants in interfaces. Interfaces define types

DefaultLabelNotLastInSwitchStmt

Best practice
Warning

The default label should be the last label in a switch statement

PositionLiteralsFirstInCaseInsensitiveComparisons

Best practice
Warning

Position literals first in String comparisons for EqualsIgnoreCase

PositionLiteralsFirstInComparisons

Best practice
Warning

Position literals first in String comparisons

PreserveStackTrace

Best practice
Warning

New exception is thrown in catch block

SwitchStmtsShouldHaveDefault

Best practice
Warning

Switch statements should have a default label

UseCollectionIsEmpty

Best practice
Warning

Substitute calls and make them more efficient. (e.g. is .useEmpty() instead of .size() == 0)

UseVarargs

Best practice
Informational

Consider using varargs for methods or constructors which take an array the last parameter.