LowFile-scopeKotlin Plug & play

Refactor nested flatMap chains

Break deep map/flatMap chains into named suspend functions or use runCatching/Result for clearer composition.

Why this matters

Improves readability and error propagation.

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

Avoid

a()?.flatMap { b(it) }?.flatMap { c(it) }?.map { d(it) }

Prefer

suspend fun step1() = a()
suspend fun step2(x: X) = b(x)
val out = step1()?.let { step2(it) }

Bad

aaa.flatMap{...}.flatMap{...}.map{...}

Good

extract steps into named functions

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