Evan Almloff
Evan Almloff
> Are events handled very differently from other attributes? The type inferences on event handlers is slightly worse for components vs elements: ```rust use dioxus::prelude::*; fn main() { dioxus::launch(|| {...
> @ealmloff Thank you for the feedback. Other than these nits, What do you think about the overall process? Do you think this is something we should proceed with to...
Can you reproduce the issue without hot patching enabled? The error you posted could be caused by hot patching changing function signatures.
That is likely an unrelated error
> I was finally able to get the behavior I saw previously (again super hard to get a reproducible error) but last night I saw the error here: > >...
I think the way we spread props is fundamentally flawed. It doesn't go through the builder, so none of the prop attributes are applied. Which means you can't spread into...
> #[cfg(feature = "web")] > fn updater(&mut self, callback: Rc) { ... } > > #[cfg(not(feature = "web"))] > fn updater(&mut self, callback: Arc) { ... } Specializing based on...
This looks similar to https://github.com/DioxusLabs/dioxus/issues/2539
Captured error has a default from implementation for any type that implements `Error`. You can display the error by formatting it like this: ```rust use dioxus::prelude::*; use thiserror::Error; fn main()...
If you are targeting dioxus desktop with fullstack, this might be the same issue as https://github.com/DioxusLabs/dioxus/issues/3689 which should be fixed by https://github.com/DioxusLabs/dioxus/pull/3693