Skip to main content
Contents

cascade_invocations

Contents
Stable
Fix available

Cascade consecutive method invocations on the same reference.

Details

#

DO Use the cascading style when successively invoking methods on the same reference.

BAD:

dart
SomeClass someReference = SomeClass();
someReference.firstMethod();
someReference.secondMethod();

BAD:

dart
SomeClass someReference = SomeClass();
...
someReference.firstMethod();
someReference.aProperty = value;
someReference.secondMethod();

GOOD:

dart
SomeClass someReference = SomeClass()
    ..firstMethod()
    ..aProperty = value
    ..secondMethod();

GOOD:

dart
SomeClass someReference = SomeClass();
...
someReference
    ..firstMethod()
    ..aProperty = value
    ..secondMethod();

Enable

#

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

analysis_options.yaml
yaml
linter:
  rules:
    - cascade_invocations

If you're instead using the YAML map syntax to configure linter rules, add cascade_invocations: true under linter > rules:

analysis_options.yaml
yaml
linter:
  rules:
    cascade_invocations: true

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