Skip to content

Conversation

@MarceloRobert
Copy link
Collaborator

@MarceloRobert MarceloRobert commented Jan 22, 2026

Changes

  • Adds a new page for the treeListing using the new endpoint
  • Updates the status type to conform with the 3-status format
  • Reorganizes routes and files
  • Refactors some component parts to be reusable between treeListings
  • Adds a banner to switch between treeListing versions

Logic for the naming of the components/pages/routes:

  • we shouldn't have to rename a whole file every time a version changes (such as "treeListing" -> "treeListingV0")
  • there shouldn't be a new route for a different version of a page, only a new subroute (note that this is not the same for the backend, where a new version should equate to a new api endpoint for discoverability)
  • the latest version of the route shouldn't need to explicit the version
  • we should avoid calling things "old" or "new" as these words are relative and may change meaning over time

How to test

Start of with data in the new treeListing table, instructions on how to populate it can be found in #1706
Check the new treeListing page and the old version. Check if the redirects are working as intended

Closes #1559

@MarceloRobert MarceloRobert self-assigned this Jan 22, 2026
@MarceloRobert MarceloRobert added the Frontend Most or all of the changes for this issue will be in the frontend code. label Jan 22, 2026
- Replaces old treeListing page with new endpoint and status format
- Reorganizes the routes and component files
- Refactors some component parts in order to be reused between treeListings
@MarceloRobert MarceloRobert force-pushed the feat/use-new-tree-listing branch from b0be2f0 to 20d453b Compare January 23, 2026 12:58
@MarceloRobert MarceloRobert marked this pull request as ready for review January 23, 2026 13:03
Copy link
Contributor

@gustavobtflores gustavobtflores left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, just a small nit, i'll pre-approve

page: formatMessage({ id: 'treeListing.treeListing' }),
gitHubLink: (
<a
href="https://github.com/kernelci/dashboard/issues"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: I think we could move this URL into a constant at that point

@MarceloRobert MarceloRobert added the enhancement New feature or request label Jan 23, 2026
Used as a link between the newer and older versions of the treeListing, should be removed after the new tree listing is stable
@MarceloRobert MarceloRobert force-pushed the feat/use-new-tree-listing branch from 20d453b to fcb7d4f Compare January 26, 2026 15:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request Frontend Most or all of the changes for this issue will be in the frontend code.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Replace current tree views with new, denormalized, table

2 participants