Skip to content

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

Closed
Magenda opened this issue Nov 18, 2019 · 3 comments
Closed

Futures and Hot Reload #31

Magenda opened this issue Nov 18, 2019 · 3 comments

Comments

@Magenda
Copy link

Magenda commented Nov 18, 2019

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!

@escamoteur
Copy link
Collaborator

What are you thinking about this as new API

Future<void> allReady();

and

Future<void> isReady<T>({Object instance, String instanceName});

instead of exposing the Future or Stream directly? With this way we get more control and I can easily correct the problem above

@escamoteur
Copy link
Collaborator

Hi, I'm just doing an overhaul of the initialization helper of GetIt.
It would be great if you could have a look at my current API proposal and give me Feedback
https://gist.github.com/c4c717518729a4c24a4ce95c10111473

@escamoteur
Copy link
Collaborator

Should be handled better with version V4.0.0 please check #46

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants