LowFile-scopeDart Plug & play

Do Not Ignore Exceptions

Always handle or log caught exceptions instead of silently ignoring them to improve debugging and maintain application stability.

Why this matters

Ignoring exceptions can hide potential bugs. Handle them properly or log them for debugging purposes.

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

Avoid

void save() {
  try {
    saveDocument();
  } catch (exception) {
  }
}

Prefer

void save() {
  try {
    saveDocument();
  } catch (exception) {
    log(exception);
  }
}

Bad

void save() {
  try {
    saveDocument();
  } catch (exception) {
  }
}

Good

void save() {
  try {
    saveDocument();
  } catch (exception) {
    log(exception);
  }
}

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