[Feature] Option for ignoreReassignment about get_it HOT 5 CLOSED

Implemented in V7.6.8

from get_it.

why not just registering in setup?

from get_it.

Also ignoreReassignment could be marked as @visibleForTesting.

why not just registering in setup?

I have a setup function the runs at the beginning, but I want to reassign one of the singletons being created there. The only way I have is verbose, I need to pass nullable instances to setup, so I can verify if they are null or not. If they are not null, I use them, so this is how we can inject fake instances for tests. This very verbose and could be immensely simplified if we had a ignoreReassignmentForTesting.

Here's an example of what I have to do now:

@override
  Future<void> setup({
    Dio? dio,
    ExampleRestDataSource? exampleRestDataSource,
    PackageInfo? packageInfo,
    ExampleRepository? ExampleRepository,
    ExampleCubit? ExampleCubit,
  }) async {
    getIt
      ..registerSingleton(dio ?? Dio())
      ..registerSingleton(exampleRestDataSource ?? ExampleRestDataSource(getIt()))
      ..registerSingleton(packageInfo ?? await PackageInfo.fromPlatform())
      ..registerSingleton(exampleRepository ??
          ExampleRepository(
            exampleRestDataSource: getIt(),
            packageInfo: getIt(),
          ))
      ..registerSingleton(exampleCubit ?? ExampleCubit(exampleRepository: getIt()));
  }

from get_it.

why not just registering in setup?

Because that yields the same result as what I outlined above. If I moveGetIt.I.registerSingleton<IFoo>(FakeFoo()); into setup, the test is still going to blow up when I call app.startup because startup registers RealFoo. Right now we have to have suboptimal code in our production code so that we can conditionally register dependencies based on whether we're testing or not.

from get_it.

OK, I think I finally understood this issue the first time, my bad. We probably should call the option something like skipDoubleRegistrations

from get_it.