-
Notifications
You must be signed in to change notification settings - Fork 21
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
Sorting in CPT Dashboard #138
base: revamp
Are you sure you want to change the base?
Conversation
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.
I like the reformatting, but I want to be able to find the real functional changes here without scanning hundreds of reformatted lines to figure out where they are. I'm going to defer this review until we can see it without the reformatting.
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.
I only got through the Python code; I'll take another look at the JavaScript.
I think this would benefit from a consistent output in the getJobs
methods, with the data/total dict rather than having the callers check whether a key exist. There are several other patterns here that we modified in #135 that I think should be carried through to this ...
@dbutenhof Let's merge 135 into the revamp branch. Once this branch is rebased with the revamp branch, all other changes will be incorporated here. |
Right ... I've gotten so used to chaining one PR on top of the other I hadn't really considered that these changes are independent of #135 and they'll get merged after that drops. So, sure: we'll review again after you've rebased. 😁 |
Oops ... I hit approve in the wrong tab. I still need to re-review this. 😁 |
@@ -0,0 +1,23 @@ | |||
# Define the keywords for sorting. |
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.
Is there a reason this is hard-coded and not retrieved from an API?
What does this apply to?
I think it would be beneficial to mention some of this in the comment.
Type of change
Description
As part of Dynamic Pagination, Sorting is moved to the backend. On clicking the arrow icon next to the table column header, hits the server with
sort
param in the payload. It takes the formatsort=<field_name>:<sort_dir>
Also, formatted the .py files with
black
formatter.Related Tickets & Documents
Checklist before requesting a review
Testing