refactor: simplify mode transitions with lookup table #41
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What
Modetype alias from inline union type.transitionsrecord mapping each mode → { next, delay }.Why
Before:
Each mode transition required a separate if-else branch, duplicating the
setTimeoutpattern 6 times.Adding or modifying a mode meant editing imperative logic.
After:
Transitionsare defined declaratively in one place.The
useEffectsimply looks up the next state and delay—no branching required.This follows the "data over code" principle and makes the state machine self-documenting.
Test