Repository navigation
fix(stream-detail): use stable key for auto-withdraw history rows (closes #1033) - #1071
Open
jdjioe5-cpu wants to merge 1 commit into
Open
jdjioe5-cpu wants to merge 1 commit into
jdjioe5-cpu wants to merge 1 commit into
Conversation
This branch had an error being deployed
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
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.
Summary
Closes #1033
This PR addresses issue #1033 by replacing the non-stable array index key (
key={idx}) on auto-withdraw history rows inapp/app/stream/[id]/page.tsxwith a stable composite key:key={${entry.timestamp}-${idx}``.Changes
app/app/stream/[id]/page.tsx:key={idx}tokey={${entry.timestamp}-${idx}`` to avoid React DOM node reuse mismatches when entries are prepended/appended.Verification
npx vitest run auto-withdraw).main('ort' strategy 0 conflicts).