swaits/dioxus
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: add attributions for crates

Browse Source
This commit is contained in:
Jonathan Kelley committed 2022-03-08 14:41:49 -05:00
1 parent 3acd643afb
commit c6fdd03a9d
3 files changed
+48 -2
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

docs/guide/src/state/liftingstate.md
+1 -2
View File
@@ -104,8 +104,7 @@ fn Title(cx: Scope) -> Element {
This is great - all is well in the world. We get precise updates, automatic memoization, and a solid abstraction. But, what happens when we want to reuse this component in another project? This component is now deeply intertwined with our global state - which might not be the same in another app.
In this case, we want to "lift" our global state out of "view" components. With `lifting`, our individual components at "leaf" position of our VirtualDom are "pure", making them easily reusable, testable, and deterministic. For instance, the "title" bar of our app might be a fairly complicated component.
In this case, we want to "lift" our global state out of "view" components. With `lifting`, our individual components at "leaf" position of our VirtualDom are "pure", making them easily reusable, testable, and deterministic.
To enable our title component to be used across apps, we want to lift our atoms upwards and out of the Title component. We would organize a bunch of other components in this section of the app to share some of the same state.