Hotreload doesn't pierce through macro contents about dioxus HOT 5 CLOSED

Hello, I recommend upgrading to the latest stable version of Dioxus, version 0.5.1. I've personally been using the git version, as fixes are constantly being pushed.

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 dioxus-cli up to date by occasionally running cargo install dioxus-cli.

It may not hurt to try a dx clean as well to see if that fixes things.

from dioxus.

@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. :-(

from dioxus.

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 I18 { src: "something.2" } component which would receive hotreloading treatment via its props, but nothing yet is plumbed for i18n in the way you're trying to use today.

from dioxus.

Nice! I will hold my breath and keep enjoying Dioxus as it is right now

from dioxus.

Nice! I will hold my breath and keep enjoying Dioxus as it is right now

from dioxus.