Preserve intialState of a cubit about cubit

[felangel]

What do you mean? It's one extra line of code haha. If you want, you can make your own custom cubit that does this for you like:

abstract class MyCubit<T> extends Cubit<T> {
  MyCubit(this.initialState) : super(initialState);
  final T initialState;
}

Then you can make your cubits all extend MyCubit instead:

class CounterCubit extends MyCubit<int> {
  CounterCubit() : super(0);

  void someMethod() {
    // you can now access the initial state via `initialState`
  }
}

This solution is the same amount of code as you would currently write minus the MyCubit class (which is a one time thing) 👍

[narcodico]

Hi @pedromassango 👋

It's not cubit's responsibility to cache your initial state.
You can have a factory constructor on your freezed data class

factory LanguageState.initial() => LanguageState(
      languages: [],
      isLoadingLanguages: true,
      loadLanguageFailure: null,
);

and use it to initialize your cubit or to emit it again when needed.

LanguageCubit() : super(LanguageState.initial());

emit(LanguageState.initial());

Hope that helps 👍

[felangel]

Hi @pedromassango 👋

You can add an initialState property to your cubit as needed 👍

class CounterCubit extends Cubit<int> {
  CounterCubit(this.initialState) : super(initialState);

  final int initialState;
}

Hope that helps 👍

[pedromassango]

Hi @pedromassango 👋

You can add an initialState property to your cubit as needed 👍

class CounterCubit extends Cubit<int> {
  CounterCubit(this.initialState) : super(initialState);

  final int initialState;
}

Hope that helps 👍

I mean, the cubit to preserve the initial state passed into it. The solution you suggested works but:

• You need to provide it via constructor
• You need to write a lot fo code for every Cubit in the project when neccessary.

[pedromassango]

I get it 👍