LowFile-scopeDart Plug & play

Extract complex conditional logic to separate methods

Move long/branchy UI decisions into named predicates or mappers to keep build methods simple.

Why this matters

Improves readability and testability of control flow.

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

Avoid

if (a && (b || c) && user.role == 'admin' && now.isAfter(deadline)) ...

Prefer

if (shouldShowAdminWarning(user, now)) ...

bool shouldShowAdminWarning(User u, DateTime now) => a && (b || c) && u.isAdmin && now.isAfter(deadline);

Bad

deep nested ifs in build()

Good

bool predicate(...) => ...; // used in build()

From the same buckets as this rule.

Critical
Avoid Empty Methods
Detect methods that have an empty body. If a method is empty, ensure that a comment is present explaining why it remains unimplemented.
maintainabilityreadability-refactor
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 Equality Operators in Loop Termination Conditions
Ensure that relational operators (`<`, `>`) are used instead of equality operators (`==`, `!=`) in loop termination conditions.
readability-refactor