empty_catches

Avoid empty catch blocks.

This rule is available as of Dart 2.0.

Rule sets: core, recommended, flutter

This rule has a quick fix available.

AVOID empty catch blocks.

In general, empty catch blocks should be avoided. In cases where they are intended, a comment should be provided to explain why exceptions are being caught and suppressed. Alternatively, the exception identifier can be named with underscores (e.g., _) to indicate that we intend to skip it.

BAD:

try {
  ...
} catch(exception) { }

GOOD:

try {
  ...
} catch(e) {
  // ignored, really.
}

// Alternatively:
try {
  ...
} catch(_) { }

// Better still:
try {
  ...
} catch(e) {
  doSomething(e);
}

To enable the empty_catches rule, add empty_catches under linter > rules in your analysis_options.yaml file:

linter:
  rules:
    - empty_catches

Unless stated otherwise, the documentation on this site reflects Dart 3.5.4. Page last updated on 2024-07-03. View source or report an issue.