-
Notifications
You must be signed in to change notification settings - Fork 254
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It is recommended to call the "commit()" method after adding instances. #835
Comments
What should we do exactly here? |
fixed |
Estou usando a versao 6.0.0+2 e ta com esse bug ainda, ou não foi fei o deploy do fix? |
The same is happening to me. I'm using flutter_modular version 6.0.3. I'm using Drift to create database code and accessor classes. class AppModule extends Module {
@override
void binds(Injector i) {
super.binds(i);
i.addSingleton(() => KInventoryDatabase());
i.addInstance<StatusesDao>(
i.get<KInventoryDatabase>().statusesDao,
);
i.addInstance<ItemsDao>(
i.get<KInventoryDatabase>().itemsDao,
);
i.addLazySingleton<StatusesService>(DriftStatusesServiceImpl.new);
i.addLazySingleton<ItemsService>(DriftItemsServiceImpl.new);
} |
@bmsrangel try to remove line |
I've tried that before, same result |
it is not clear where to call the commit method |
Same issue. Where to call commit method? |
**What should we do exactly here? **
The text was updated successfully, but these errors were encountered: