Best practice for StateNotifierProvider different states as data

[AhmedLSayed9]

I've a case where I need state as initial when user enter ResendActivateEmailScreen and another state as success to navigate user from ResendActivateEmailScreen to another screen when the call is success (By using ref.listen inside ResendActivateEmailScreen build).

I've created the state for my StateNotifier using Freezed as following:

@freezed
class ResendActivateEmailState with _$ResendActivateEmailState {
  const factory ResendActivateEmailState.initial() = _Initial;

  const factory ResendActivateEmailState.loading() = _Loading;

  const factory ResendActivateEmailState.error(Failure failure) = _Error;

  const factory ResendActivateEmailState.success() = _Success;
}

It's working fine, but as I'm trying to use AsyncValue for my Providers, I'm wondering if it's better to use a mix of AsyncValue and Freezed instead? so my idea is something like this:

@freezed
class ResendActivateEmailState with _$ResendActivateEmailState {
  const factory ResendActivateEmailState.initial() = _Initial;
  const factory ResendActivateEmailState.success() = _Success;
}

class ResendActivateEmailNotifier extends StateNotifier<AsyncValue< ResendActivateEmailState >> {
  ResendActivateEmailNotifier(this.ref) : super(const AsyncData(ResendActivateEmailState.initial()));

  resend(String email) async {
    state = const AsyncLoading();
    final _result = await callApiByRepo(email);
    _result.fold(
      (failure) {
        state = AsyncError(failure, stackTrace: failure.stackTrace);
      },
      (success) {
        state = const AsyncData(ResendActivateEmailState.success());
      },
    );
  }
}

or maybe using enum here too instead of Freezed as I don't need to store data in the state.

What do you think? the unique way of using just Freezed or a mix of AsyncValue and freezed/enum to try to unify with using AsyncValue in other providers?