HighFile-scopeKotlin Plug & play

Add comprehensive error logging

Log failures with operation name, key identifiers, and exception; prefer structured logging (fields).

Why this matters

Accelerates debugging and enables reliable alerting.

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

Avoid

println(e)

Prefer

logger.error("payment_failed", mapOf("orderId" to orderId, "userId" to userId, "err" to e))

Bad

e.printStackTrace()

Good

logger.error("op_failed", mapOf("op" to op, "err" to e))

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