Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Align inference pipeline card/option styling #172952
Align inference pipeline card/option styling #172952
Changes from 8 commits
ef2f6ce
122002e
e7a8166
4f19547
77c63ce
f58aad0
a4e1569
456b9de
458637c
95a0506
90c4585
e8f094c
3a3ba93
a7a8fc5
fb1a34b
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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 see some discrepancies with the model-related subcomponents here vs in the model selection component within the pipeline configuration flyout. Let's make sure we address these in the unified ML design:
TrainedModelHealth
), for example the downloading/downloaded states all map to "Not started". If we want to display more fine-grained states, we'll need to use model details fromMlModel
in the pipeline card.text_embedding
) vs a user-friendly title in the model selector ("Dense Vector Text Embedding"). (We may not have the space the display the full title here.)I'll link to this comment in the unified UX Jira.
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.
Good callouts! I could address the first point in this PR by shrinking the button to not include the status badge, but IMO it's nice to have a larger button area, especially since there's no other click action to associate with the status badge. WDYT?
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.
To me it doesn't come intuitively that a badge is clickable. I'd either restrict clickability to the "..." button only, or turn the status badge into a (non-empty) button. But this is a good question to the UX folks, maybe they have some suggestions.
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.
Ok, since this an open question for the UX folks, I will keep this as-is for now and we can adjust in a follow-up PR.