LowFile-scopeRuby Plug & play

Avoid Rescuing the `Exception` Class

Identify rescue Exception statements and suggest replacing them with rescue StandardError to avoid catching critical system exceptions.

Add to Mesrai Open workspace

Why this matters

Rescuing Exception captures critical system-level errors like NoMemoryError, preventing proper application termination and potentially masking serious issues.

Bad vs. good

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

Avoid

begin
  risky_operation
rescue Exception
  puts "An error occurred"
end

Prefer

begin
  risky_operation
rescue StandardError => error
  puts "An error occurred: #{error.message}"
end

Related rules

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

Why this matters

Bad vs. good

Related rules

Avoid equality operators in loop termination conditions

Avoid Returning Null in Non-Async Task Methods

Avoid Using Boolean Expressions in `except` Statements

Why this matters

Bad vs. good

Related rules

Avoid equality operators in loop termination conditions

Avoid Returning Null in Non-Async Task Methods

Avoid Using Boolean Expressions in `except` Statements