-
Notifications
You must be signed in to change notification settings - Fork 610
Hot reload support? #14
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
Did some research on this. Not sure if it will be useful to anyone
|
I haven't looked at reload support yet, so I don't have any extra insight into what all is necessary. I think we'll need to discuss with Flutter developers how reloading should work in the embedding model though (e.g., it might make sense for it to be exposed as an embedding API). At a high level, I don't think we want people to have to launch applications with |
Thanks for the answer. I got it to work somehow. Perhaps by switching to flutter's master branch. For anyone interested these are the steps required:
I think I could improve the fork and prepare it for merge:
|
hi @szotp I got this error while using that hacks
|
Now that attach mode has been added to Dart Code, adding hot reload should be doable without any hackery since it's exposed via the observatory's reloadSources command. Assuming that works as well as the daemon reloads (I haven't tested yet) it would just be a case of adding a Dart Code command to invoke it. |
With IntelliJ I was able to attach the debugger using the "Dart Remote Debug" run configuration. However it looks like hot reload isn't supported yet when attaching in this way. There is an open issue to implement this. See: flutter/flutter-intellij#2250 |
Based on recent discussion in a Dart Code issue, hot reload via the observatory relies on a hook that's registered by flutter-tools, so just attaching to a desktop process won't allow hot reload after all. It looks like we'll probably need either some kind of hook in the Flutter tools, or a desktop runner that provides the same functionality. |
Is there a good news? |
No, see my last comment. |
Provides basic instructions for debugging the Flutter side of a desktop application, since the normal approaches for Flutter debugging require some modifications on desktop. Related to issue google#14 and issue google#164, although doesn't fully address either.
I consider this a strong selling point for developers. Hot reload is frigging awesome! |
I think this issue can be closed because hot reload have been implemented in |
The reason it's still open is that the current instructions still use the |
Moved to flutter/flutter#30707 (solving the (Debugging.md will continue to be updated as the need for special handling changes.) |
Hi, I'm interested in adding support for hot reload and debugging, but I don't know enough about flutter/dart ecosystem. Would implementing flutter/flutter#5043 solve the problem or is it more complicated?
Something like
flutter connect http://127.0.0.1:49278/
to completely bypass device detection, etc.The text was updated successfully, but these errors were encountered: