HighFile-scopeJava Plug & play

Avoid Empty Catch Blocks

Ensure that catch blocks contain meaningful exception handling logic and do not remain empty.

Why this matters

Empty catch blocks swallow exceptions, making it difficult to diagnose issues. Instead, log the exception or handle it appropriately.

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

Avoid

try {
    process();
} catch (IOException e) {}

Prefer

try {
    process();
} catch (IOException e) {
    log.error("Error processing", e);
}

Bad

try {
    process();
} catch (IOException e) {}

Good

try {
    process();
} catch (IOException e) {
    log.error("Error processing", e);
}

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