-
-
Notifications
You must be signed in to change notification settings - Fork 153
Futures and Hot Reload #31
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
Comments
What are you thinking about this as new API
and
instead of exposing the Future or Stream directly? With this way we get more control and I can easily correct the problem above |
Hi, I'm just doing an overhaul of the initialization helper of GetIt. |
Should be handled better with version V4.0.0 please check #46 |
Is there any way to make future instances work with hot reload?
For an explanation on the issue please read here: https://stackoverflow.com/questions/58326960/flutter-get-it-and-futurebuilder-not-working-with-hot-reload
Thanks!
The text was updated successfully, but these errors were encountered: