-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
add ui_next dashboard #8402
add ui_next dashboard #8402
Conversation
Build succeeded.
|
@@ -316,6 +316,9 @@ def get(self, request, format=None): | |||
if period == 'month': | |||
end_date = start_date - dateutil.relativedelta.relativedelta(months=1) | |||
interval = 'days' | |||
elif period == 'two_weeks': |
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.
@ryanpetrello this look good to you? Just want to make sure we're not sneaking something by y'all without a review.
Now that we've got recent jobs/templates tabbed out at the bottom my first instinct was... why not have all 3 things in tabs like: then there would be little need for scrolling. Of course, this would mean that recent jobs is now an extra click away. I don't feel strongly about this, it just came to mind as an option. It really depends on how this page is actually used/what users care about seeing. @trahman73 @wenottingham 👍 / 👎 ? (This could easily be changed in the future as well if we'd rather just stick to the current UX initially.) |
jtActions && Object.prototype.hasOwnProperty.call(jtActions, 'POST'); | ||
const canAddWFJT = | ||
wfjtActions && Object.prototype.hasOwnProperty.call(wfjtActions, 'POST'); | ||
// spreading Set() returns only unique keys |
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.
Do we still need this? Not sure which line it's referencing.
I think this is looking fantastic @jlmitch5! Curious about |
@unlikelyzero @tiagodread I don't anticipate a tremendous amount of change/refactor on this PR so it's probably safe for you all to start getting familiar with it. |
@mabashian we are going to do a bug bash on it on wednesday and take a first look at this tomorrow |
Note: we will need to put in //to be implemented for #8401 |
@mabashian That's not a bad idea to combine all 3 views into a tabbed card as shown. I don't think it's a big deal to have to click into the Recent Jobs and Recent Templates tab to get to that content. I'm curious about more opinions as I don't really know how this page is currently used. |
Build succeeded.
|
|
85075e9
to
5f4d6da
Compare
Build failed.
|
@trahman73 @jlmitch5 @jakemcdermott the 3 tab design also improves client-side performance. Our weighted lighthouse score improved by 3/100 points between revisions |
@jlmitch5 A bug-free PR!
The only point of feedback is that we'd like to have this a bit more testable.
We have an associated PR that we'd like to have merged alongside this PR. It should contain:
|
recheck |
Build failed.
|
^^ I think this is a legitimate failure
Test probably need to be updated after changing to the 3 tabs view |
Build failed.
|
Build succeeded.
|
@jlmitch5 we're almost done with the tests. We just need unique IDs for the tabs and the cards. Is that something you can get in tomorrow? |
Build succeeded.
|
Associated Tests in 5622 |
Build succeeded (gate pipeline).
|
Link #8400 #6756
This pr adds the dashboard to ui_next. The big changes are: