Deduplicate refreshNodeStatuses guard and node-row rebuild#552
Merged
Conversation
Extract the shared 'still current chain + nonce' guard into updateNodesIfCurrent and the currentNode/buildNodeRows rebuild into State.refreshedNodeRows, applied to the per-node result and final update blocks. The empty and loading blocks keep their distinct guards. Behavior unchanged — node statuses smoke-tested on emulator.
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
1 participant
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.
Extract the repeated "still current chain + nonce" guard into updateNodesIfCurrent and the currentNode/buildNodeRows rebuild into State.refreshedNodeRows, applied to the per-node result and final update blocks of refreshNodeStatuses. The empty and loading blocks keep their distinct guards. No behavior change — node statuses (latency, latest block, selected node) smoke-tested on emulator.