Skip to content

fix(launchplan): show every launch plan - #923

Open
1fanwang wants to merge 2 commits into
flyteorg:masterfrom
1fanwang:fix-launchplan-count-typo
Open

fix(launchplan): show every launch plan#923
1fanwang wants to merge 2 commits into
flyteorg:masterfrom
1fanwang:fix-launchplan-count-typo

Conversation

@1fanwang

@1fanwang 1fanwang commented Jun 21, 2026

Copy link
Copy Markdown
Contributor

TL;DR

Projects with more than about 30 launch plans cannot reach the rest of the list.

Before this change, a project with 64 launch plans stops scrolling around row 30.
After this change, both list views render through the final launch plan.

Type

  • Bug Fix
  • Feature
  • Plugin

Are all requirements met?

  • Code completed
  • Smoke tested
  • Unit tests added
  • Code documentation added. Not applicable: no public API changed.
  • Any pending items have an associated Issue. No pending items.

Complete description

The virtualizer never receives the page's scroll container, so it renders only its
first window. Render the launch-plan results directly in the card and table views.

Manual check:

  1. Open a project with 64 launch plans.
  2. Scroll to the end in table view, then repeat in card view.

Before this change, both views stop around row 30. With this change, both reach row 64.
Regression tests check that every supplied result becomes a table row or card.

Tracking Issue

N/A

Follow-up issue

N/A

@1fanwang
1fanwang force-pushed the fix-launchplan-count-typo branch from 3c7258b to 9bbe292 Compare June 21, 2026 08:41
@1fanwang 1fanwang changed the title fix(launchplan): render the full launch plan list instead of clipping it fix(launchplan): show every launch plan Aug 20, 2026
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
1fanwang force-pushed the fix-launchplan-count-typo branch from 9bbe292 to 8795275 Compare August 24, 2026 10:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant