CriticalFile-scopeRuby Plug & play

Ensure `if...elsif` Constructs End with an `else` Clause

Verify that all if...elsif constructs include a final else clause. If else is missing, ensure there is a comment explaining why all cases are covered.

Add to Mesrai Open workspace

Why this matters

When an if statement has multiple elsif branches, it should always end with an else clause. This ensures all possible cases are handled, preventing unintended behavior.

Bad vs. good

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

Avoid

if x == 0
  doSomething
elsif x == 1
  doSomethingElse
end

Prefer

if x == 0
  doSomething
elsif x == 1
  doSomethingElse
else
  raise 'An error has occured'
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