-
-
Notifications
You must be signed in to change notification settings - Fork 734
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
Hotreload doesn't pierce through macro contents #2438
Comments
Hello, I recommend upgrading to the latest stable version of Dioxus, version My guess is that the change that triggers the reload is actually a full rebuild, and not an instant template update. I also recommend keeping It may not hurt to try a |
@luveti thanks, I just uploaded to 0.5.4, but the issue remains: any change that is not textual is taken into account for the recompiling, but textual changes are not caught. :-( |
The issue here is you're modifying code in a macro which we can't figure out if should be hotreloaded or not. This PR #2258 is adding an entirely new, more powerful form of hotreloading, but still wouldn't work with the contents of macros. We do have longer term plans to ship actual, legitimate horeloading of Rust code but that's not available in any form, yet. With #2258 you could use an |
Nice! I will hold my breath and keep enjoying Dioxus as it is right now |
Nice! I will hold my breath and keep enjoying Dioxus as it is right now |
[Linux, Debian testing]
Hi,
When launching my fullstack app with dx serve --hot-reload --platform fullstack or any variant of this,
I get the console log telling me
Dioxus @ v0.5.0-alpha.2 [17:24:29]
Listening on 127.0.0.1:8080
spinning up hot reloading
hot reloading ready
🔥 Hot Reload WebSocket connected
🔮 Finding updates since last compile...
finished
😳 Hot Reload WebSocket disconnected
And the hot reload doesn't work.
I have to manually relaunch the dx command at each change in the rsx block.
It only occurs when I change the text of a p block for example. As if only changing text from a block was not caught.
A change from
p { "Hello world"}
to
p { "Hello world 2"}
won't trigger anything, but a change from
to
will.
Is it a normal behavior?
Thanks
The text was updated successfully, but these errors were encountered: