feat: optimistic update loop for task Verify Quality button - #142
Merged
N-thnI merged 6 commits intoJun 24, 2026
Conversation
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
Implement an optimistic update loop in TaskCard.tsx so that clicking Verify Quality instantly reflects changes in the UI before Soroban consensus finality.
Problem
Currently, users must wait several seconds for chain indexing to see updates, leading to a laggy experience.
Solution
Shift task status indicators to a loading/pending state immediately on user confirmation.
Increment the visible vote count badge locally by +1 right away.
If the Soroban transaction fails, revert the local changes gracefully and show a toast notification.
Acceptance Criteria
UI responds instantly on vote cast.
Pending state clearly visible.
Errors handled with rollback + toast.
Verified via latency tests.
Closes #2