HighFile-scopePython Plug & play

Ensure Functions Use `return` Consistently

Detect functions that mix `return` statements with values and those without. Inconsistent return usage can lead to unpredictable behavior.

Why this matters

Mixing `return` statements that return values with those that don’t can lead to confusing, unpredictable behavior.

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

Avoid

def foo(a): # Noncompliant, function will return "true" or None
  if a == 1:
    return True
  return

Prefer

def foo(a):
  if a == 1:
    return True
  return False

Bad

def foo(a): # Noncompliant, function will return "true" or None
  if a == 1:
    return True
  return

Good

def foo(a):
  if a == 1:
    return True
  return False

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