-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[ML][UX]: Consistent Layout and UI Enhancements for ML Pages #203813
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.
response-ops
changes ok
Pinging @elastic/ml-ui (:ml) |
* Titles for the cases toast messages | ||
*/ | ||
export const TITLES = { | ||
CHANGE_POINT_DETECTION: 'Change point detection', |
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.
Should these be internationalized?
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.
Change point chart
might be better here. Change point chart added to case
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.
Done in: #7f408c6
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.
Sorry I'd forgotten that it's possible to multi-select charts to add to a case - can a plural condition be added for Change point chart
/ Change point charts
?
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.
Added plural for Change point charts
.
Also Change point table
message when the table view is selected in: #847d00e
pageTitle={ | ||
<> | ||
{currentDataView.getName()} | ||
{/* TODO: This management section shouldn't live inside the header */} |
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.
Are you planning on doing this in this PR?
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 we can tackle it, but it would be nice to find a different place for this menu to reside.
Otherwise, it's being wrapped within an <h1>
tag, which doesn't seem right.
If @joana-cps suggests a better location for the button, we can definitely move it outside the header.
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 agree that we need to find a different place for this menu. We can do this in a separate issue.
x-pack/platform/plugins/shared/ml/public/application/explorer/anomaly_timeline.tsx
Show resolved
Hide resolved
@@ -321,7 +321,7 @@ export const SeriesControls: FC<PropsWithChildren<SeriesControlsProps>> = ({ | |||
|
|||
return ( | |||
<div data-test-subj="mlSingleMetricViewerSeriesControls"> | |||
<EuiFlexGroup direction={direction}> | |||
<EuiFlexGroup direction={direction} gutterSize="s"> |
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.
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.
Updated the detector dropdown to have a min width in: #cd56f03
To preserve vertical alignment, I propose wrapping controls as the width decreases. I don't see any way to keep everything in a single row while maintaining good alignment.
WDYT?
Screen.Recording.2024-12-19.at.11.19.43.mov
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 looks good, I think it is a good solution.
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.
Agree with @joana-cps - this is working well.
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 and visually LGTM. Thanks Robert for these improvements!
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.
Code LGTM, just added some minor suggestions.
@@ -90,10 +90,6 @@ interface DatePickerWrapperProps { | |||
/** | |||
* Boolean flag to set use of flex group wrapper | |||
*/ | |||
flexGroup?: boolean; | |||
/** |
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.
Looks like you accidentaly removed the comment for the next prop and not flexGroup
.
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 catch, done in: #d73ab5d
/** | ||
* Titles for the cases toast messages | ||
*/ | ||
export const TITLES = { |
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.
Suggest to make this a bit more specific like CASES_TOAST_MESSAGES_TITLES
.
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.
Agree, done in: #7f47fad
/** | ||
* Titles for the cases toast messages | ||
*/ | ||
export const TITLES = { |
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.
Again, suggest to make this const more specific like CASES_TOAST_MESSAGES_TITLES
.
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.
Done in: #7f47fad
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 latest changes and LGTM.
Just left one suggestion about a plural case for the change point charts. Would be good to get that in too.
💚 Build Succeeded
Metrics [docs]Module Count
Async chunks
Page load bundle
Unknown metric groupsasync chunk count
ESLint disabled line counts
Total ESLint disabled count
History
cc @rbrtj |
Starting backport for target branches: 8.x https://github.com/elastic/kibana/actions/runs/12465668093 |
💔 All backports failed
Manual backportTo create the backport manually run:
Questions ?Please refer to the Backport tool documentation |
Friendly reminder: Looks like this PR hasn’t been backported yet. |
2 similar comments
Friendly reminder: Looks like this PR hasn’t been backported yet. |
Friendly reminder: Looks like this PR hasn’t been backported yet. |
Summary
Add to
action buttons across various ML pages - see: [ML][UX]: Updates to ML embeddable 'Add to' action #184109Anomaly Detection
pages - see: #2043948px
(gutterSize = 's'
)Exploration around new
Add to
actions buttons - the right column is the most recent one, see: #184109 :Toasts:
Other changes: