logic and types separation #4
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The current codebase mixes game logic with React component code in GameContext.tsx. Additionally, type definitions are scattered across files, making it difficult to maintain consistent types across the application.
Solution
Move game logic to a dedicated folder
Create a centralized types file
Implement proper separation between game logic and UI components
Changes Made
New File Structure.
Moved core game functions from GameContext.tsx to game/board.ts:
Centralized Type Definitions:
Created types.ts with shared interfaces
Enhanced Type Safety:
Added type guards and runtime checks isValidRow
Benefit
Game logic can now be tested independently of React components