-
Notifications
You must be signed in to change notification settings - Fork 58
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
EmptyState implementation inconsistency with Vanilla Framework #1071
Comments
Had a small chat today with @lukasSerelis and he specified that the Empty State design from Vanilla Framework is the one we should use in the web apps as well. |
Thanks for confirming that. I'm not sure why this inconsistency was introduced, but will be good to fix that to avoid confusion. |
@bartaz I'm currently looking into how Vanilla Framework implemented the Empty State and the implementations of all 3 types of Empty States differ. Are we only concerned with implementing the No content Empty State in this component? |
Yes, the Vanilla docs for Empty State pattern are very generic and cover variety of cases (search, 404, etc). For apps the most relevant is "no content" empty state, so that was meant to be covered by this React component. |
Closing as completed in #1076 |
Vanilla Framework's design of
EmptyState
component can be found here and thereact-components
library's design can be found here. The image is rendered to the left of the text in Vanilla Framework, while it is rendered on top of the text inreact-components
library.The text was updated successfully, but these errors were encountered: