Jonathan Kelley
f2b1c6d97f
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.
29 lines
745 B
Rust
29 lines
745 B
Rust
//! 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}" }
|
|
}
|
|
}
|