Fix/settlements panel reentrancy#346
Open
chuks68 wants to merge 2 commits into
Open
Conversation
…xtend tests for card layout
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.
Closes #142
Summary
This PR resolves a re-entrancy bug in the
SettlementsPanelcomponent (SettlementsPanel.tsx).The Problem
The
loadMorefunction inSettlementsPanelpreviously only checked ifstate.status !== "ready"before fetching more settlements. Although the "Load more" button is disabled during loading (disabled={loadingMore}), other trigger paths (such as keyboard shortcuts or rapid Enter presses) could callloadMoreconcurrently before React updated the disabled state. This resulted in duplicate concurrent fetches.The Solution
Added an early return guard: