refactor(ui): introduce ResourceListPage and standardize resource lis…#3305
Open
Baluduvamsi2006 wants to merge 1 commit intoapache:masterfrom
Open
refactor(ui): introduce ResourceListPage and standardize resource lis…#3305Baluduvamsi2006 wants to merge 1 commit intoapache:masterfrom
Baluduvamsi2006 wants to merge 1 commit intoapache:masterfrom
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
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.
What this PR does
This PR introduces a reusable
ResourceListPagecomponent and refactors existing resource list pages to use it.Previously, each resource list page (Services, Routes, Consumers, Upstreams, etc.) duplicated the same ProTable setup, pagination handling, toolbar logic, page header, and empty-state behavior. This duplication made maintenance harder and increased the risk of inconsistencies.
With this change:
ResourceListPageAdditionally, this PR improves E2E test stability by tightening selectors, improving cross-platform path handling, and reducing flakiness during parallel execution.
Why this change is needed
Checklist