-
Notifications
You must be signed in to change notification settings - Fork 167
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
Update modals and generate meaningful k8s name for images #1529
Update modals and generate meaningful k8s name for images #1529
Conversation
@vconzola Could you please check the UX updates in this PR? Thanks! |
lgtm |
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.
Tested all changes on my end, looks fine.
/lgtm
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.
Some changes needed
eaf0e22
to
8de654f
Compare
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.
Looking good... let me run a few visual tests. One question...
> | ||
<FlexItem>{obj.display_name}</FlexItem> | ||
<FlexItem> | ||
<ImageErrorStatus image={obj} /> | ||
</FlexItem> | ||
<ResourceNameTooltip resource={convertBYONImageToK8sResource(obj)}> | ||
{obj.display_name} | ||
</ResourceNameTooltip> | ||
<ImageErrorStatus image={obj} /> | ||
</Flex> |
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.
This seems like you'll not get spacing, why this change?
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 think this is the magic of Flex, they become flex items by nature and it auto fits them. So although looks weird in code, this works out.
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.
FYI, you're going to run into a conflict -- Gage kept the FlexItem
s. Perhaps you should match his implementation to avoid conflicts
I think this works great overall. However, we should have a sit down with UX and get feedback on the keyboard actions. I'm not sure I like the escape/enter action flows -- double escape closes the modal without warning. Keyboard flow doesn't really get you back in once you escape out (we should probably focus the "add software" at that point -- but it is the next tab index so it's reasonable) I think we are already are aware of the issue with a bad image -- I just worry it tosses everything away and it's not just inconvenient for an image name. Which I think now with the added flow of keyboard actions, one could quickly lose more. Probably useful to incubate these and get feedback across the board on them though. |
8de654f
to
e233810
Compare
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.
FYI
> | ||
<FlexItem>{obj.display_name}</FlexItem> | ||
<FlexItem> | ||
<ImageErrorStatus image={obj} /> | ||
</FlexItem> | ||
<ResourceNameTooltip resource={convertBYONImageToK8sResource(obj)}> | ||
{obj.display_name} | ||
</ResourceNameTooltip> | ||
<ImageErrorStatus image={obj} /> | ||
</Flex> |
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.
FYI, you're going to run into a conflict -- Gage kept the FlexItem
s. Perhaps you should match his implementation to avoid conflicts
/approve @DaoDaoNoCode get someone else on the team to verify it again, I unfortunately lost my window to test the code again. Looks good though, thanks for making the desired changes. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: andrewballantyne, manaswinidas The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@andrewballantyne Sure, let me squash the commits first. |
10f9b48
to
9750213
Compare
a4411a9
to
22aa0ff
Compare
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.
it all works as described. few UX related issues though, not breaking.
- invalid images will show enabled but be greyed out, you have to refresh for the UI to correct itself and show it to be not enabled and greyed out.
- when adding software/packages, in edit mode for a row
- make edits in one of the text boxes
- cancel with either the X button or ESC
- edit the row again
- the last edits that were canceled are still there
22aa0ff
to
f3e776c
Compare
f3e776c
to
3494a78
Compare
/lgtm |
Closes #1433 #1435 #1388 #1326
Description
This PR did the following things:
Enable
column in the table, for the error images, it will set default to disabled and the user cannot enable it. Also, add the sort to theEnable
column as @vconzola requested here Refactor BYON images table #1506 (comment)byon-${timestamp}
, but now it'scustom-${translated-k8s-name}
wheretranslated-k8s-name
is the translation of the display name that user inputs. Also, add a tooltip next to the image name so the user could easily locate the image stream resource on the cluster.Highlights: Refactor the table for adding/editing packages and software in the modal. Take the software as an example, when the user starts to add software or edit software, he will be in the edit mode, which only allows the user to confirm or abandon the current change (the user cannot edit multiple lines at the same time and cannot submit or exit the modal).
What's more, when the user hits
Enter
in the edit mode, it will automatically confirm the current row and move to the next row. If the row is already the last row, it will create a new entry, which helps the user to quickly input and move on without clicking with the mouse every time. When the user hitsEsc
in the edit mode, it will abandon the current change of the row and exit the edit mode.Edit mode: close button hidden, Submit and Cancel button disabled, other rows cannot be edited and removed, either
Non-edit mode: You can do anything you want
How Has This Been Tested?
quay.io/opendatahub/workbench-images:jupyter-minimal-ubi8-python-3.8-pr-89
) and incorrect path (likequay.io/opendatahub/workbench-images:invalid-tag
) and you could check the status of the toggle on theEnable
column. Try to create more and sort by theEnable
columnTest Impact
TBD
Request review criteria:
Self checklist (all need to be checked):
If you have UI changes:
After the PR is posted & before it merges:
main