PreferWidgetMethodsOverClassesRule class

Warns when small widgets could be extracted as methods instead of classes.

Since: v1.3.0 | Updated: v4.13.0 | Rule version: v2

This is an opinionated rule - not included in any tier by default.

Pros of widget methods:

• Less boilerplate code
• Simpler for very small UI pieces
• Access to parent widget state without passing

Cons (why some teams prefer widget classes):

• Widget classes enable better rebuild optimization
• Easier to add const constructors
• Better separation of concerns
• More testable in isolation

Note: Only flags private StatelessWidgets with simple build methods. Complex widgets with fields or multiple methods are not flagged.

Example

BAD (with this rule enabled):

// Small widget that could be a method
class _MyIcon extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return Icon(Icons.star, color: Colors.yellow);
  }
}

GOOD:

// In parent widget:
Widget _buildIcon() {
  return Icon(Icons.star, color: Colors.yellow);
}

Note: This rule suggests methods for SIMPLE widgets. Complex widgets with state or many parameters should remain as classes.