HighFile-scopeDart Plug & play

Wrap Uri.parse in try-catch blocks

Use try/catch (or Uri.tryParse with validation) around Uri.parse to guard against FormatException and invalid inputs.

Why this matters

Prevents crashes from malformed URLs and enables clear error reporting.

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

Avoid

final uri = Uri.parse(link); // may throw

Prefer

final uri = Uri.tryParse(link);
if (uri == null || !uri.hasScheme) {
  logger.warning('Invalid URL', {'link': link});
  return;
}
// safe to use uri

Bad

Uri.parse(input)

Good

final u = Uri.tryParse(input); if (u != null) open(u);

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