codify "platform" into resolution logic, server-fn/fullstack overhaul (#4596)
overhaul dioxus fullstack using a new implementation of server_fn This PR is a complete rewrite of dioxus fullstack designed to improve compatibility with axum and to fix a number of compilation errors based on feature flag unification plumbing through macros.
This commit is contained in:
1 parent
8421c3aef0
commit
f2b1c6d97f
424 files changed
+17284
-6624
No files matched your search
@@ -0,0 +1,28 @@
|
||||
//! This example demonstrates how to create a generic component in Dioxus.
|
||||
//!
|
||||
//! Generic components can be useful when you want to create a component that renders differently depending on the type
|
||||
//! of data it receives. In this particular example, we're just using a type that implements `Display` and `PartialEq`,
|
||||
|
||||
use dioxus::prelude::*;
|
||||
use std::fmt::Display;
|
||||
|
||||
fn main() {
|
||||
dioxus::launch(app);
|
||||
}
|
||||
|
||||
fn app() -> Element {
|
||||
rsx! {
|
||||
generic_child { data: 0 }
|
||||
}
|
||||
}
|
||||
|
||||
#[derive(PartialEq, Props, Clone)]
|
||||
struct GenericChildProps<T: Display + PartialEq + Clone + 'static> {
|
||||
data: T,
|
||||
}
|
||||
|
||||
fn generic_child<T: Display + PartialEq + Clone>(props: GenericChildProps<T>) -> Element {
|
||||
rsx! {
|
||||
div { "{props.data}" }
|
||||
}
|
||||
}
|
||||
Reference in new issue
Block a user