Repository navigation
Conversation
1fanwang
force-pushed
the
fix-launchplan-count-typo
branch
from
June 21, 2026 08:41
3c7258b to
9bbe292
Compare
The launch plan table and card views virtualized against
document.getElementById('scroll-element'), which is null in this layout, so the
virtualizer had no scroll container and rendered the wrong number of rows. The
table view also read result?.length (the lodash `result` function, always
truthy) instead of results?.length. Render the results directly with stable keys.
Signed-off-by: 1fanwang <1fannnw@gmail.com>
The fix changes both launch-plan views, but the regression covered only the table. Exercise the card view with enough results to fail under the old detached virtualizer. Signed-off-by: 1fanwang <1fannnw@gmail.com>
1fanwang
force-pushed
the
fix-launchplan-count-typo
branch
from
August 24, 2026 10:25
9bbe292 to
8795275
Compare
Signed-off-by: 1fanwang <1fannnw@gmail.com>
Contributor
Author
|
@kumare3 could you review when you have time? |
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.
Read then delete this section
Release version rules
TL;DR
Launch-plan views can omit results when the virtualizer has no usable scroll element. Both views now render the launch-plan results they receive.
Type
Are all requirements met?
Complete description
The card and table views render the supplied results directly with stable item keys. Loading and empty states are unchanged.
Testing Done
I rendered the actual card and table views in jsdom with their normal providers and child components. The probe supplies 64 launch plans, checks the rendered cards and rows, and checks the empty table.
With Node 16.19.0 and the checkout's installed dependencies, save the source below as launch_plan_repro.cjs in the repository root and run:
React also emitted these row-markup warnings:
Reproducer source: launch_plan_repro.cjs
I did not run a browser scrolling test or a live-backend smoke test. ESLint and Prettier checks passed.
Tracking Issue
N/A
Follow-up issue
N/A