1f2daf233e
Fixed property access bug introduced in previous commit: **Issue**: - DefensiveSetup.vue was accessing `gameState.runners.third` and `runners.first/second/third` - GameState type doesn't have a `runners` property - Caused TypeScript error: "Property 'runners' does not exist on type 'GameState'" **Fix**: - Changed to use correct properties: `on_first`, `on_second`, `on_third` - Updated infieldDepthOptions: `props.gameState?.on_third` (line 163) - Updated outfieldDepthOptions: destructure `on_first, on_second, on_third` (line 178) - Updated hasRunners check: `on_first || on_second || on_third` (line 184) **Why**: GameState uses individual nullable properties for runners, not a nested object. This matches the backend Pydantic model structure. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| Decisions | ||
| Game | ||
| Gameplay | ||
| Substitutions | ||
| UI | ||
| CLAUDE.md | ||