LowFile-scopeDart Plug & play

Define dialog handlers once to avoid duplication

For confirm/cancel flows, define common callbacks (confirm/cancel) once and reuse across dialogs.

Why this matters

Reduces copy-paste mistakes and ensures consistent analytics/logging on actions.

Bad vs. good

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

Avoid

TextButton(onPressed: () { log('cancel'); Navigator.pop(context); })
TextButton(onPressed: () { log('cancel'); Navigator.pop(context); })

Prefer

void onCancel(BuildContext c) { logger.info('dialog_cancel'); Navigator.pop(c); }
TextButton(onPressed: () => onCancel(context), child: const Text('Cancel'))

More snippets

Bad

inline Cancel handlers everywhere

Good

shared onCancel/onConfirm helpers

Related rules

From the same buckets as this rule.

Critical
Avoid Duplicating String Literals
Store repeated string literals in constants or variables to improve maintainability and reduce redundancy.
duplication-complexitymaintainability
Critical
Avoid Redundant `None` Comparisons
Identify cases where `x is None` or `x is not None` is used redundantly when `x` is always or never `None`. This may indicate a deeper logic issue.
duplication-complexityreadability-refactor+1
High
Avoid Functions That Always Return the Same Value
Identify functions that return the same value regardless of input. This may indicate poor design or a logic error.
duplication-complexityreadability-refactor+1

Why this matters

Bad vs. good

More snippets

Related rules

Avoid Duplicating String Literals

Avoid Redundant `None` Comparisons

Avoid Functions That Always Return the Same Value

Why this matters

Bad vs. good

More snippets

Related rules

Avoid Duplicating String Literals

Avoid Redundant `None` Comparisons

Avoid Functions That Always Return the Same Value