HighFile-scopeDart Plug & play

Prefer `is!` Over `!is` for Type Checks

Use is! instead of !is for type checking to prevent confusion and ensure consistent behavior.

Why this matters

Using is! instead of !is avoids confusion with null assertion syntax and improves code clarity.

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

Avoid

void main(dynamic s) {

  if (s !is String) { // Noncompliant
    print('s is not a String!');
  }

}

Prefer

void main(dynamic s) {

  if (s is! String) {
    print('s is not a String!');
  }

}

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