-
Notifications
You must be signed in to change notification settings - Fork 842
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
[Discuss] Skeleton component and usage #3474
Comments
Haven't looked too into this, but wanted to drop this somewhere it wouldn't be forgotten about: |
Padding this with a link to an old discussion of using this in tables as well. #476 |
👋 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. |
Added this to a 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. |
Hello folks 👋 I'm enjoying using EUI to build interfaces, and I want to thank you guys for all this precious work 🙏 Speaking about the need for Skeleton primitives, I totally agree, and at the moment I'm keeping up only by heavily hacking the So as per CONTRIBUTING guidelines, I'm posting this to mark my intent to work on this new NOTE: I'm comparing skeleton components of other design systems and trying to end up with a proposal that sticks with the EUI structure as much as possible, but of course, this will overlap with the See you soon |
PR link #6502 |
Closed by #6558 |
@bevacqua reminded us that folks are using
<EuiLoadingContent lines={3} />
quite a bit downstream. We've also seen some usage in the SIEM apps that @andrew-goldstein and @XavierM put together. We had a discussion as a team about how to handle these types of loading states and came away with the following discussion points:We need more skeleton primitives for off the cuff usage
To "fake" components we probably need skeleton solutions to the following:
Long term, it might be nice to build skeleton modes into the components directly
We rambled a little bit about whether EUI components should actually have a
skeleton
boolean prop that would just automatically fake content as needed.The text was updated successfully, but these errors were encountered: