如何扩展ThemeData并实现extension非空以消除空安全检查？

由于Flutter框架的ThemeData.extensions设计为可空类型Iterable<ThemeExtension<dynamic>>?，导致每次调用extension<T>()都需要做空检查。以下是几种实用的解决思路：

1. 给ThemeData封装非空扩展方法 #

通过扩展ThemeData，为每个自定义主题扩展添加非空的getter方法，同时给自定义扩展类添加默认兜底实现：

首先，给自定义的ThemeExtension类添加默认构造或静态默认方法：

class CustomTextTheme extends ThemeExtension<CustomTextTheme> {
  final TextStyle h1Bold;

  CustomTextTheme({required this.h1Bold});

  // 默认兜底实现
  factory CustomTextTheme.defaultTheme() {
    return CustomTextTheme(
      h1Bold: TextStyle(fontSize: 24, fontWeight: FontWeight.bold),
    );
  }

  @override
  CustomTextTheme copyWith({TextStyle? h1Bold}) {
    return CustomTextTheme(h1Bold: h1Bold ?? this.h1Bold);
  }

  @override
  CustomTextTheme lerp(ThemeExtension<CustomTextTheme>? other, double t) {
    if (other is! CustomTextTheme) return this;
    return CustomTextTheme(
      h1Bold: TextStyle.lerp(h1Bold, other.h1Bold, t)!,
    );
  }
}

class CustomThemeExtension extends ThemeExtension<CustomThemeExtension> {
  final Color primaryBrand;

  CustomThemeExtension({required this.primaryBrand});

  factory CustomThemeExtension.defaultColors() {
    return CustomThemeExtension(primaryBrand: Colors.blue);
  }

  @override
  CustomThemeExtension copyWith({Color? primaryBrand}) {
    return CustomThemeExtension(primaryBrand: primaryBrand ?? this.primaryBrand);
  }

  @override
  CustomThemeExtension lerp(ThemeExtension<CustomThemeExtension>? other, double t) {
    if (other is! CustomThemeExtension) return this;
    return CustomThemeExtension(
      primaryBrand: Color.lerp(primaryBrand, other.primaryBrand, t)!,
    );
  }
}

然后封装ThemeData的扩展：

extension NonNullThemeExtensions on ThemeData {
  CustomTextTheme get customTextTheme {
    return extension<CustomTextTheme>() ?? CustomTextTheme.defaultTheme();
  }

  CustomThemeExtension get customColors {
    return extension<CustomThemeExtension>() ?? CustomThemeExtension.defaultColors();
  }
}

使用时直接调用封装后的getter，无需空检查：

Text(
  carouselModel.title,
  style: themeState.customTextTheme.h1Bold.copyWith(
    color: themeState.customColors.primaryBrand,
  ),
  textAlign: TextAlign.center,
)

2. 初始化主题时强制包含所有自定义扩展 #

确保App的ThemeData（包括亮色、深色主题）在初始化时就包含所有自定义扩展，这样调用extension<T>()时永远不会返回null，此时可以安全使用非空断言!：

// 定义亮色主题
final lightTheme = ThemeData(
  brightness: Brightness.light,
  extensions: [
    CustomTextTheme(
      h1Bold: TextStyle(fontSize: 24, fontWeight: FontWeight.bold, color: Colors.black),
    ),
    CustomThemeExtension(primaryBrand: Colors.blue),
  ],
);

// 定义深色主题
final darkTheme = ThemeData(
  brightness: Brightness.dark,
  extensions: [
    CustomTextTheme(
      h1Bold: TextStyle(fontSize: 24, fontWeight: FontWeight.bold, color: Colors.white),
    ),
    CustomThemeExtension(primaryBrand: Colors.lightBlue),
  ],
);

// 在MaterialApp中使用
MaterialApp(
  theme: lightTheme,
  darkTheme: darkTheme,
  home: const YourHomePage(),
)

使用时直接用非空断言：

Text(
  carouselModel.title,
  style: themeState.extension<CustomTextTheme>()!.h1Bold.copyWith(
    color: themeState.extension<CustomThemeExtension>()!.primaryBrand,
  ),
  textAlign: TextAlign.center,
)

这种方式的核心是确保主题初始化时不遗漏任何自定义扩展，只要保证这一点，非空断言就是绝对安全的。

3. 通过状态管理封装非空主题扩展 #

如果使用Provider、Riverpod等状态管理工具，可以在主题提供者中提前处理空检查，对外暴露非空的扩展实例：

以Provider为例：

class ThemeProvider extends ChangeNotifier {
  late ThemeData _currentTheme;

  ThemeProvider() {
    // 初始化时使用包含所有扩展的主题
    _currentTheme = lightTheme;
  }

  // 对外暴露非空的自定义扩展
  CustomTextTheme get customTextTheme => _currentTheme.extension<CustomTextTheme>()!;
  CustomThemeExtension get customColors => _currentTheme.extension<CustomThemeExtension>()!;

  // 切换主题，确保切换后的主题也包含所有扩展
  void toggleTheme() {
    _currentTheme = _currentTheme == lightTheme ? darkTheme : lightTheme;
    notifyListeners();
  }
}

UI层使用时直接调用Provider的getter：

final themeProvider = Provider.of<ThemeProvider>(context);
Text(
  carouselModel.title,
  style: themeProvider.customTextTheme.h1Bold.copyWith(
    color: themeProvider.customColors.primaryBrand,
  ),
  textAlign: TextAlign.center,
)

为什么直接扩展ThemeData重写extensions没用？ #

因为ThemeData是不可变类，其extensions属性是final的，框架的extension<T>()方法是基于原类的extensions集合实现的，重写extensions不会改变extension<T>()的查找逻辑，所以这种方式无法解决空检查问题。

内容的提问来源于stack exchange，提问作者Fi Li Ppo