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
If we use the `TITLE` atom in another component, we can cause updates to flow between components without calling render or diffing either component trees:
106
106
107
107
```rust
108
-
constReceiver:Component<()>=|cx|{
108
+
constReceiver:Component=|cx|{
109
109
lettitle=use_signal(&cx, &TITLE);
110
110
log::info!("This will only be called once!");
111
111
rsx!(cx,
@@ -132,7 +132,7 @@ Dioxus automatically understands how to use your signals when mixed with iterato
Copy file name to clipboardExpand all lines: docs/guide/src/concepts/errorhandling.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@
4
4
Astute observers might have noticed that `Element` is actually a type alias for `Option<VNode>`. You don't need to know what a `VNode` is, but it's important to recognize that we could actually return nothing at all:
Copy file name to clipboardExpand all lines: docs/guide/src/hello_world.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -135,7 +135,7 @@ fn App(cx: Scope) -> Element {
135
135
Writing `fn App(cx: Scope) -> Element {` might become tedious. Rust will also let you write functions as static closures, but these types of Components cannot have props that borrow data.
0 commit comments