Evan Almloff

This is also related to https://github.com/DioxusLabs/dioxus/issues/1688 which is a more broad issue about how to pass state, and layers to the server in dioxus fullstack

I cannot reproduce this issue with dioxus `0.5.0` or the latest commit of the main branch of dioxus: https://github.com/ealmloff/reproduce-dioxus-fullstack-2193 The page takes 1 second to reload, but does not reload...

I cannot reproduce an issue when importing a component created with the `#[component]` macro from another crate with dioxus `0.5.0`. Here is my [setup](https://github.com/ealmloff/fail-repoduce-2228). That error message is also very...

> ## `rsx` syntax enhancements > This is more to open discussion about the possibility, but I think there are some areas where `rsx` could improve : > > *...

> Yet `dx new` insists that I choose a single platform/renderer. And after doing so, if I run `dx init` it gives an error that Cargo.toml already exists. Choosing the...

> How about TUI and mobile? What constraints do I need to adhere to in order to work on all supported platforms? Eg, I don't think I can expect TUI...

Expanding the component name to a struct will cause lints on any components that use the `component_name` syntax with an underscore instead of upper camel case

Flakey windows tests are fixed in https://github.com/DioxusLabs/dioxus/pull/2332 🙂

https://github.com/DioxusLabs/dioxus/pull/2298 fixes a similar error. It might fix your project as well

I can think of two different ways to fix this issue: 1) Introduce an extra layer of interior mutability in every ReadOnlySignal that allows you to update the signal it...