Question: Is GetIt capable of changing singleton in runtime? about get_it HOT 5 CLOSED

  /// By default it's not allowed to register a type a second time.
  /// If you really need to you can disable the asserts by setting[allowReassignment]= true
  bool allowReassignment = false;

By changing to true this mean I need to change the code in a package, or just copy and paste the whole _GetItImplementation into my app code just to config it. Should have the better way. I agree with @ezzabuzaid

Before calling GetIt.instance.registerSingleton ensure that you run GetIt.instance.allowReassignment = true;, and this will allow you to reregister the type again, without editing the source code. @PhilipPurwoko

from get_it.

it would be very helpful if there allowReassignment on service level registration

  _locator.registerSingleton<T>(instance, allowReassignment: true);

from get_it.

Why on registration level? what's wrong with globally enable it if you really need it?
In many cases unregister and then register anew is the cleaner options. Possible using a scope.

from get_it.

sure you can do this. Either use two different registrations at startup or reregister the type again but therefore you have to set

  /// By default it's not allowed to register a type a second time.
  /// If you really need to you can disable the asserts by setting[allowReassignment]= true
  bool allowReassignment = false;

to true.

Does this solve your problem?

from get_it.

  /// By default it's not allowed to register a type a second time.
  /// If you really need to you can disable the asserts by setting[allowReassignment]= true
  bool allowReassignment = false;

By changing to true this mean I need to change the code in a package, or just copy and paste the whole _GetItImplementation into my app code just to config it. Should have the better way. I agree with @ezzabuzaid

from get_it.