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: blog/2023-10-02-what-is-a-state-machine/index.mdx
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -45,7 +45,7 @@ Visually, state machines are just boxes and arrows. The building blocks of a sta
45
45
46
46
### States
47
47
48
-
A [state](/docs/states/intro) represents a particular situation, mode, or status that something can be in. For instance, an e-commerce site’s order can be in the _Pending_, _Shipped_, _Delivered_, or _Returned_ states. Each of these is a finite state, contributing to the entire lifecycle of an order.
48
+
A [state](/docs/state-machines-and-statecharts#states) represents a particular situation, mode, or status that something can be in. For instance, an e-commerce site’s order can be in the _Pending_, _Shipped_, _Delivered_, or _Returned_ states. Each of these is a finite state, contributing to the entire lifecycle of an order.
49
49
50
50
<p>
51
51
<ThemedImage
@@ -59,7 +59,7 @@ A [state](/docs/states/intro) represents a particular situation, mode, or status
59
59
60
60
Finite states are **deterministic**, meaning that something can only be in exactly one finite state at a time. An order cannot be in both the _Pending_ and _Delivered_ states at the same time, just like you can’t be in both the _Asleep_ and _Awake_ states simultaneously.
61
61
62
-
State machines always start at an **[initial state](/docs/states/initial-states)** and may end up in a **[final state](/docs/states/final-states)**, indicating that the state machine is “done” and can no longer transition to any other state.
62
+
State machines always start at an **[initial state](/docs/state-machines-and-statecharts#initial-state)** and may end up in a **[final state](/docs/state-machines-and-statecharts#final-state)**, indicating that the state machine is “done” and can no longer transition to any other state.
63
63
64
64
### Events
65
65
@@ -77,7 +77,7 @@ Events are occurrences; they’re a record that something happened. Using the pr
77
77
78
78
### Transitions
79
79
80
-
A state [transition](/docs/transitions-and-events/intro) describes how a system “moves” from one state to another. These are the arrows between the states, labeled by the event that causes the transition to occur.
80
+
A state [transition](/docs/transitions) describes how a system “moves” from one state to another. These are the arrows between the states, labeled by the event that causes the transition to occur.
81
81
82
82
In state machines, transitions always happen immediately. For example, an order can be _Pending_ for some time (almost frustratingly so), but when the _item shipped_ event occurs, it immediately transitions to the _Shipped_ state.
0 commit comments