refactor: remove deprecated parameters and legacy single-peer code#1325
Merged
Conversation
- Remove deprecated fogOfWarRef from usePostProcessing hook and call sites - Remove deprecated wallPlacementPreviewRef from useGameInput hook and call sites - Remove legacy single-peer validation fallback in Game.ts (multi-peer system is now fully set up) - Remove redundant setDataChannel calls from useLobbySync.ts (addPeer handles this) - Fix README.md documentation drift: update file paths for networking implementation The multi-peer system via addPeer()/peerChannels is now the sole implementation path. Legacy fields (remotePeerId, dataChannel) are still present in multiplayerStore but no longer needed for command validation - they can be removed in a follow-up PR. https://claude.ai/code/session_01MopZftCMNSsXVjQF2igzRv
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 multi-peer system via addPeer()/peerChannels is now the sole implementation path. Legacy fields (remotePeerId, dataChannel) are still present in multiplayerStore but no longer needed for command validation - they can be removed in a follow-up PR.
https://claude.ai/code/session_01MopZftCMNSsXVjQF2igzRv