prefer-single-setstate

v1.30.0

style

effort: 2m

teams+

Suggests merging multiple consecutive setState invocations into a single invocation.

Example

❌ Bad:

class _SomeState extends State<StatefulWidget> {
  void someMethod() {
    // ...

    setState(() {
      // some logic
    });

    // LINT: Prefer calling 'setState' only once.
    //  Try moving all callback logic to the previous invocation.
    setState(() {
      // another
    });
  }
}

✅ Good:

class _SomeState extends State<StatefulWidget> {
  void someMethod() {
    setState(() {
      // some logic
      // another
    });
  }
}

Related Rules

• avoid-empty-setstate
• avoid-unnecessary-setstate
• use-setstate-synchronously