feat: Socket.IO client integration for persistent WS state updates - #139
Merged
Conversation
Meet-hybrid
force-pushed
the
feat/socketio-client
branch
from
June 22, 2026 21:54
4b15b39 to
70f3044
Compare
…esetSocketClientForTests
Contributor
|
please ensure checks pass |
…abet connect button
…ilder mocks for SDK compat - logger: pass Uint8Array directly to subtle.decrypt instead of extracting .buffer via bytesToArrayBuffer — cross-realm ArrayBuffer from jsdom is rejected by Node's webcrypto.subtle - VoteButton: add missing mockUseNetwork variable, remove duplicate mock - txBuilder: call .build() on SorobanDataBuilder, add results array with auth/xdr to match newer @stellar/stellar-sdk expectations
4 tasks
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.
Description
Establish a persistent WebSocket connection to deliver real‑time state updates.
Problem
Users currently need to manually refresh pages to see changes.
Solution
Implemented a socket.io client in src/components/.
Event‑driven updates automatically refresh local state on incoming events.
Optimized performance by syncing with local state instead of full reloads.
Secure WebSocket handshake enforced.
Acceptance Criteria
State auto‑refreshes on events.
Verified via latency tests.
No manual refresh required.
Closes #27