Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ui] Handle jobs pagination #19806

Closed
6 of 8 tasks
philrenaud opened this issue Jan 23, 2024 · 0 comments
Closed
6 of 8 tasks

[ui] Handle jobs pagination #19806

philrenaud opened this issue Jan 23, 2024 · 0 comments
Assignees
Labels
hcc/bff Internal: server-side stuff in a client-side world stage/accepted Confirmed, and intend to work on. No timeline committment though. type/enhancement
Milestone

Comments

@philrenaud
Copy link
Contributor

philrenaud commented Jan 23, 2024

Handle pagination of the endpoint(s) provided from #19339

Phase 1:

  • Establish a blocking query watcher with per_page that updates whenever jobs within that range have updated
  • Observe changes to the N+1th job (where N is per_page) that updates the next_token parameter and, to the user, makes the "next" button clickable
  • Establish prev/next buttons
  • Establish "prev" functionality when the user has refreshed the page at an already-paginated point (Note: this is tricky because there is no concept of a prev_token, and reverse=true doesn't appear to work on the jobs endpoint)
  • Set up searching and filtering options #20425
  • Handle parent jobs' children status #20491
  • Now that the endpoint doesn't return child jobs, have a parent job loaded directly look them up for child job table purposes

Phase 2:

  • Port aggregateAllocStatus as a filterable/queryable parameter for our endpoint
@philrenaud philrenaud added type/enhancement hcc/bff Internal: server-side stuff in a client-side world labels Jan 23, 2024
@philrenaud philrenaud self-assigned this Jan 23, 2024
@philrenaud philrenaud added this to the 1.8.0 milestone Jan 23, 2024
@lgfa29 lgfa29 added the stage/accepted Confirmed, and intend to work on. No timeline committment though. label Feb 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hcc/bff Internal: server-side stuff in a client-side world stage/accepted Confirmed, and intend to work on. No timeline committment though. type/enhancement
Projects
Status: Done
Development

When branches are created from issues, their pull requests are automatically linked.

2 participants