HighFile-scopeDart Plug & play

Use rethrow to preserve stack traces

When re-emitting a caught exception, use `rethrow` instead of `throw e` to keep the original stack trace.

Why this matters

Original stack traces are essential for accurate debugging and error grouping.

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

Avoid

catch (e) {
  throw e; // resets stack
}

Prefer

catch (e, st) {
  logger.severe('operation failed', e, st);
  rethrow; // preserves stack
}

Bad

catch (e) { throw e; }

Good

catch (e, st) { rethrow; }

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