🟡 GameContext: context provider never wired into the app #65
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
File:
src/components/game/GameContext.tsxThe
GameContextsystem (provider + hooks) exists as a parallel architecture to the direct Zustand store hooks used inpage.tsx.GameProvideris never wrapped around the app inpage.tsxor any layout. OnlyMemorySlotPicker.tsxusesuseGameContext, which would throw an error if rendered since the provider is missing.Impact: The context-based architecture is non-functional.
MemorySlotPickerwould crash at runtime.Fix: Either wrap the app with
GameProviderinpage.tsxorlayout.tsx, or remove the context system entirely if the direct Zustand hook pattern is the preferred architecture.[priority: 4] BROKEN FEATURE — GameContext provider never wired into the app, context unavailable everywhere.
Starting work on #65. Analysis complete: GameContext system (Provider, hooks, context-create, types) is entirely dead code. MemorySlotPicker is the only consumer of useGameContext but is itself orphaned (never rendered). The app uses direct Zustand hooks throughout. Decision: remove the entire GameContext system to eliminate dead code and the confusing parallel architecture.
Fixed. Removed the entire dead GameContext system:
Total: 625 lines of dead code removed across 6 files. No TS errors introduced. The app uses direct Zustand hooks throughout and never needed the context layer.