-
Notifications
You must be signed in to change notification settings - Fork 110
Add sorting for clusters and query history page columns #752
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
base: main
Are you sure you want to change the base?
Conversation
CI build seemed to have failed with an unrelated error - |
Could you add screenshots to PR description when you modify UI code? |
Sure, done |
return a.routingGroup.localeCompare(b.routingGroup); | ||
}} | ||
filters={ | ||
[...new Set(backendData?.map(b => b.routingGroup))] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if backendData
is undefined this may become new Set([undefined])
, perhaps default to empty array
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if backendData is undefined, it will be new Set(undefined) which will give an empty set. So filters array will be simply empty array so i think it is ok like this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
return a.routingGroup.localeCompare(b.routingGroup); | ||
}} | ||
filters={ | ||
[...new Set(backendData?.map(b => b.routingGroup))] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if backendData is undefined, it will be new Set(undefined) which will give an empty set. So filters array will be simply empty array so i think it is ok like this.
@@ -19,3 +19,6 @@ ij_java_doc_align_param_comments = false | |||
|
|||
[*.yml] | |||
indent_size = 2 | |||
|
|||
[*.tsx] | |||
indent_size = 2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please separate a commit. This change is unrelated to "Add sorting for clusters and query history page columns".
Description
Added sort options for clusters based on name, queued query count and running query count.
Added filter option for routingGroup and sort options for routignGroup and submission time in query history page.
Additional context and related issues
Clusters page header [3 new sort icons on Name, Queued, Running]:

History Page [Sort and Filter option on RoutingGroup] -

Release notes
( ) This is not user-visible or is docs only, and no release notes are required.
( X) Release notes are required, with the following suggested text: