What is the best practice for using an external library's enum with Hive?

[kouroku-room]

I understood that the enum implemented in MyApp should use @HiveType annotation as shown in the link below.
https://docs.hivedb.dev/#/custom-objects/generate_adapter?id=enums

But there are times when I want to save the enum of an external library.
(e.g., save ThemeMode from material library and manage app-specific ThemeMode)
https://api.flutter.dev/flutter/material/ThemeMode.html

How do you guys implement such a case?

---

I have come up with the following two methods

1. Create TypeAdapter for ThemeMode.

class ThemeModeAdapter extends TypeAdapter<ThemeMode> {
  @override
  int get typeId => 100;

  final _default = ThemeMode.system;

  @override
  ThemeMode read(BinaryReader reader) {
    final name = reader.readString();
    return ThemeMode.values.asNameMap()[name] ?? _default;
  }

  @override
  void write(BinaryWriter writer, ThemeMode obj) {
    writer.writeString(obj.name);
  }
}

This method has the following drawbacks

• If the enum name is changed due to a library update, it will flow to the default value.
• It is hard to notice if the enum structure is changed by library update.

---

2. Create a similar enum in MyApp and use a switch expression at the point of value acquisition.

part 'my_enum.g.dart';

@HiveType(typeId: 110)
enum MyThemeMode {
  @HiveField(0)
  system,

  @HiveField(1)
  light,

  @HiveField(2)
  dark,
  ;

  const MyThemeMode();

  ThemeMode getThemeMode() {
    return switch (this) {
      MyThemeMode.system => ThemeMode.system,
      MyThemeMode.light => ThemeMode.light,
      MyThemeMode.dark => ThemeMode.dark,
    };
  }

  static MyThemeMode fromThemeMode(ThemeMode themeMode) {
    return switch (themeMode) {
      ThemeMode.system => MyThemeMode.system,
      ThemeMode.light => MyThemeMode.light,
      ThemeMode.dark => MyThemeMode.dark,
    };
  }
}

  ThemeMode getThemeMode() {
    final MyThemeMode myThemeMode = _box.get('ThemeMode', defaultValue: MyThemeMode.system) as MyThemeMode;
    return myThemeMode.getThemeMode();
  }

  Future<void> setThemeMode(ThemeMode themeMode) async {
    return _box.put('ThemeMode', MyThemeMode.fromThemeMode(themeMode));
  }

This method has the following drawbacks

• Large amount of code.
• Because the results are passed by human code rather than generated, it is easy to make mistakes in the values passed due to human errors.

---

I would appreciate it if you could share your thoughts on best practices.

In both cases, we need to add code when registering a new enum to Hive.
So I would be most happy to see a convenient feature like isar's enumerated annotation!
https://pub.dev/documentation/isar/latest/isar/Enumerated-class.html