mirror of
https://github.com/DioxusLabs/dioxus
synced 2024-12-25 03:53:08 +00:00
508c560320
This change switches back to the original `ctx<props>` syntax for commponents. This lets lifetime elision to remove the need to match exactly which lifetime (props or ctx) gets carried to the output. As such, `Props` is currently required to be static. It *is* possible to loosen this restriction, and will be done in the future, though only through adding metadata about the props through the Props derive macro. Implementing the IS_STATIC trait is unsafe, so the derive macro will do it through some heuristics. For now, this unlocks sharing vnodes from parents to children, enabling pass-thru components, fragments, portals, etc.
36 lines
1.1 KiB
Rust
36 lines
1.1 KiB
Rust
//! Example: RecoilCallback
|
|
//! ------------------------
|
|
//! This example shows how use_recoil_callback can be used to abstract over sets/gets.
|
|
//! This hook provides a way to capture the RecoilApi object. In this case, we capture
|
|
//! it in a closure an abstract the set/get functionality behind the update_title function.
|
|
//!
|
|
//! It should be straightforward to build a complex app with recoil_callback.
|
|
use dioxus_core::prelude::*;
|
|
use recoil::*;
|
|
|
|
const TITLE: Atom<&str> = |_| "red";
|
|
|
|
fn update_title(api: &RecoilApi) {
|
|
match *api.get(&TITLE) {
|
|
"green" => api.set(&TITLE, "yellow"),
|
|
"yellow" => api.set(&TITLE, "red"),
|
|
"red" => api.set(&TITLE, "green"),
|
|
_ => {}
|
|
}
|
|
}
|
|
|
|
static App: FC<()> = |ctx| {
|
|
let title = use_read(ctx, &TITLE);
|
|
let next_light = use_recoil_api(ctx, |api| move |_| update_title(&api));
|
|
|
|
rsx! { in ctx,
|
|
div {
|
|
"{title}"
|
|
button { onclick: {next_light}, "Next light" }
|
|
}
|
|
}
|
|
};
|
|
|
|
fn main() {
|
|
wasm_bindgen_futures::spawn_local(dioxus_web::WebsysRenderer::start(App))
|
|
}
|