You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
as described here, by the component macro that doesn't "like" the separate crate thing ?
I didn't have issue when it was in the same crate.
While the new Component is shorter and easier to read, this macro should not be used by library authors since you have less control over Prop documentation.
by prop documentation, you mean system registration or user facing documentation (that one shouldn't cause the issue above) ?
I really really like this component macro for the simplicity, so is there a way to make it work ?
Thanks!
The text was updated successfully, but these errors were encountered:
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.
That error message is also very common if you have mismatched versions of dioxus between different crates. It could happen if you rely on the git version of dioxus in one crate and the 0.5 version in another crate or dioxus-router = "0.5" with dioxus = "0.4"
Dioxus 0.5.0. alpha 2
Linux
Full stack app
Hi,
Currently rewriting some app I had in TS into Rust.
I want to create many reusable components for my projects, so I've created them in a separate crate that I will import at will in different projects.
The issue lies in the fact that the router and #[component] don't seem happy:
main.rs
interface.rs
---interface
-----route.rs
-----static_analysis.rs
-----dynamic_analysis.rs
route.rs:
the other culprit, Modal, used in StaticAnalysis and co:
I think that the issue is my calling strategy:
as described here, by the component macro that doesn't "like" the separate crate thing ?
I didn't have issue when it was in the same crate.
While the new Component is shorter and easier to read, this macro should not be used by library authors since you have less control over Prop documentation.
by prop documentation, you mean system registration or user facing documentation (that one shouldn't cause the issue above) ?
I really really like this component macro for the simplicity, so is there a way to make it work ?
Thanks!
The text was updated successfully, but these errors were encountered: