LowFile-scopeJava Plug & play

Use Try-With-Resources for Resource Management

Ensure that resources such as streams or file handlers are managed using try-with-resources to avoid leaks.

Why this matters

Failing to use try-with-resources can lead to resource leaks, as manually closing resources is error-prone and harder to maintain.

Side-by-side examples engineers can pattern-match during review.

Avoid

FileInputStream fis = new FileInputStream("file.txt");
try {
    // Read file
} finally {
    fis.close();
}

Prefer

try (FileInputStream fis = new FileInputStream("file.txt")) {
    // Read file
}

Bad

FileInputStream fis = new FileInputStream("file.txt");
try {
    // Read file
} finally {
    fis.close();
}

Good

try (FileInputStream fis = new FileInputStream("file.txt")) {
    // Read file
}

From the same buckets as this rule.

Critical
Avoid equality operators in loop termination conditions
Check if loops use equality operators (== or !=) in termination conditions. These can lead to infinite loops if the condition is never met exactly. Instead, use relational operators like < or > for safer loop termination.
error-handlingreadability-refactor
Critical
Avoid Returning Null in Non-Async Task Methods
Returning null from a Task or Task<T> method causes a NullReferenceException if awaited. Use Task.CompletedTask or Task.FromResult<T>(null) instead.
error-handlingreadability-refactor+1
Critical
Avoid Using Boolean Expressions in `except` Statements
Detect `except` clauses that use `or` or `and` to catch multiple exceptions. This does not work as intended. Recommend using a tuple of exceptions instead.
error-handlingstack-python