LowFile-scopeKotlin Plug & play

Log warning for unhandled cases

In when/else or default branches, log a warning with the unexpected value to surface silent failures.

Why this matters

Makes edge cases visible before they become incidents.

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

Avoid

when (status) {
  "ok" -> {}
  else -> {}
}

Prefer

when (status) {
  "ok" -> {}
  else -> logger.warn("unknown_status", mapOf("status" to status))
}

Bad

else -> {}

Good

else -> logger.warn("unexpected", mapOf("v" to v))

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