-
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
Clean up error state of Ingest Pipelines drag and drop list items. #137244
Clean up error state of Ingest Pipelines drag and drop list items. #137244
Conversation
Pinging @elastic/platform-deployment-management (Team:Deployment Management) |
13668c3
to
dedac7c
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.
<EuiFlexGroup gutterSize="none" alignItems="center"> | ||
<EuiFlexItem> |
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.
Since there's only one flex item now, you can probably remove this flex group/item wrapper too.
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.
Nice spot!
@cchaos I'd love to align those items the way you suggested, but I can't see a way to do it given the structure of the components and the use of flexbox to maintain alignment on the x axis. I was planning on just accepting the misalignment in the error state. What are your thoughts? |
You should be able to just bump up the button icon size to Beneficially, this gives a better (larger) hit target for those buttons. |
Thanks @cchaos! I couldn't use |
.pipelineProcessorsEditor__form__dragAndDropList__grabIcon { | ||
height: $euiSizeXL; | ||
width: $euiSizeXL; | ||
display: flex; | ||
align-items: center; | ||
justify-content: center; | ||
} |
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.
Or you can just add padding since you already know it's always going to be a compressed input with a small icon.
.pipelineProcessorsEditor__form__dragAndDropList__grabIcon { | |
height: $euiSizeXL; | |
width: $euiSizeXL; | |
display: flex; | |
align-items: center; | |
justify-content: center; | |
} | |
.pipelineProcessorsEditor__form__dragAndDropList__grabIcon { | |
padding-top: $euiSizeS; | |
} |
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.
Ah yeah, my example assumed you were using gutterSize
.
💚 Build Succeeded
Metrics [docs]Async chunks
History
To update your PR or re-run it, just comment with: |
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.
Sass and screenshots 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.
Changes LGTM, @cjcenizal! Thanks a lot for fixing this, also verified the fix locally.
…lastic#137244) (cherry picked from commit 405c904)
…lastic#137244) (cherry picked from commit 405c904)
💔 Some backports could not be created
Note: Successful backport PRs will be merged automatically after passing CI. Manual backportTo create the backport manually run:
Questions ?Please refer to the Backport tool documentation |
…137244) (#137612) (cherry picked from commit 405c904) Co-authored-by: CJ Cenizal <[email protected]>
…137244) (#137613) (cherry picked from commit 405c904) Co-authored-by: CJ Cenizal <[email protected]>
While investigating #124027, I noticed that the error state for the Grok processor patterns list looked wonky:
There's a second error icon that's being manually rendered on top of the error icon built into EUI. That second error icon displays the error message in a tooltip when you hover over it.
I fixed this by removing the manual error icon and using the EuiFormRow component to render the message. I think this is both an aesthetic and a usability improvement because you know longer need to "look with your mouse" to find the error message, you can just look with your eyes.
I'm backporting this as far back as is allowed because it's relatively non-invasive and it's a bugfix.