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
Copy file name to clipboardExpand all lines: docs/hyper-state/README.md
-4Lines changed: 0 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,11 +5,7 @@
5
5
The easiest way to understand HyperState is by example. If you you did not see the Tic-Tac-Toe example, then **[please review it now](client-dsl/interlude-tic-tac-toe.md)**, as we are going to use this to demonstrate how to use the `Hyperstack::State::Observable` module.
6
6
7
7
In our original Tic-Tac-Toe implementation the state of the game was stored in the `DisplayGame` component. State was updated by
8
-
<<<<<<< Updated upstream
9
8
"bubbling up" events from lower level components up to `DisplayGame` where the event handler updated the state.
10
-
=======
11
-
"bubbling up" events from lower level components up to `DisplayGame` where the event hander updated the state.
12
-
>>>>>>> Stashed changes
13
9
14
10
This is a nice simple approach but suffers from two issues:
15
11
+ Each level of lower level components must be responsible for bubbling up the events to the higher component.
0 commit comments