create a new instance even if dispose is not completed after resetLaz… #284
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In app i need to
resetLazySingleton
indispose
(sync) method in statefull widget. My service dispose method is async and takes long time. Once i am back in widget,Get.I<Foo>()
returns me same instance, with on going dispose. For now, the only way to avoid that is to register dispose function as non-Future, like:but here,
await resetLazySingleton<Foo>()
will not await my dispose function and nowhere i am able to wait for it. Also from convention, i don't see a point, where i would need to get again (almost) disposed instance - so i think its buggy.I think:
resetLazySingleton<Foo>(); return Get.I<Foo>();
should return a new instance;await resetLazySingleton<Foo>()
should await for dispose function with Future type.