LowFile-scopeRuby Plug & play

Use Descriptive Exception Variable Names

Ensure that exception variables in `rescue` blocks use meaningful titles instead of generic ones like `e`.

Why this matters

Naming exception variables generically (`e`) makes debugging harder. Use meaningful titles that describe the type or context of the error.

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

Avoid

begin
  risky_operation
rescue => e
  puts e.message
end

Prefer

// (no example provided)

Bad

begin
  risky_operation
rescue => e
  puts e.message
end

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