-
Notifications
You must be signed in to change notification settings - Fork 844
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
[EuiSteps] Add more flexibility/customizability #4492
Comments
I am working on this. |
Hey @git-anurag-hub , thanks for the interest in this one, but it's going to need more design thought on how best to handle these requests. I'd recommend grabbing from our list of |
Okay np @cchaos |
👋 Hey there. This issue hasn't had any activity for 180 days. We'll automatically close it if that trend continues for another week. If you feel this issue is still valid and needs attention please let us know with a comment. |
I'll keep this one open, but it's a more long-term goal. |
👋 Hey there. This issue hasn't had any activity for 180 days. We'll automatically close it if that trend continues for another week. If you feel this issue is still valid and needs attention please let us know with a comment. |
In our recent refresh to Index Lifecycle Management, we have a need to present options in a vertical timeline-like format to indicate the life cycle of data. Our design includes a set of icons that tie together vertically with a line, beside a set of panels that house the various options for that step. I suppose semantically speaking, this is closer to
EuiSteps
, but visually we feltEuiComment
got us closer to what we wanted.So admittedly, I'm not sure which component this request should target. It seems
EuiComment
is closest. Below are the list of requirements/requests:large
,update
,...) separate from the comment block styling (currently choosingupdate
styles the corresponding block differently)Image reference (from elastic/kibana#90291):
Annotated version:
Again, perhaps it makes more sense to expand on the
EuiSteps
component to allow for these options as that is more aligned to our use case. And we keep EuiComment more strict to a comment/activity feed.If we use the
EuiSteps
component (unsure if the above requests would still be valid or solve themselves):And as a side note, the
EuiComment
component feels less like Amsterdam than other components (rather, the difference between v7 and Amsterdam is less noticeable—namely the use of borders around a panel/block).Tagging for awareness: elastic/kibana#88671
The text was updated successfully, but these errors were encountered: