AssignmentToNonFinalStatic
Possible unsafe assignment to a non-final static field in a constructor.
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.
Possible unsafe assignment to a non-final static field in a constructor.
Avoid creating BigDecimal with a decimal (float/double) literal. Use a String literal
An instanceof check is being performed on the caught exception. Create a separate catch clause for this exception type.
Do not start a literal by 0 unless its an octal value
Avoid equality comparisons with Double.NaN
Check the value returned by the skip() method of an InputStream to see if the requested number of bytes has been skipped.
This usage of the Collection.toArray() method will throw a ClassCastException.
Ensure that resources like this PipedWriter object are closed after use
Use equals() to compare object references.
Dont use floating point for loop indices. If you must use floating point
Avoid idempotent operations (like assigning a variable to itself).
Avoid modifying an outer loop incrementer in an inner loop for update expression
The null check here is misplaced; if the variable is null there will be a NullPointerException
A switch statement does not contain a break
Class cannot be instantiated and does not provide any static methods or fields
A non-case label was present in a switch statement
Non-static initializers are confusing
Ensure you override both equals() and hashCode()
Avoid returning from a finally block
When instantiating a SimpleDateFormat object
Do not use if statements that are always true or always false
Use explicit locale when doing a String.toLowerCase()/toUpperCase() call
We use cookies to improve your site experience, including analytics cookies to understand how you use our product and design better experiences. Please read our Cookie Policy.