-
Notifications
You must be signed in to change notification settings - Fork 888
feat: Improve empty states for workspaces and templates #1950
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
Conversation
className?: string | ||
buttonClassName?: string |
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.
Thought: One thing to consider here is mimicking MUIs API.
These use a classes
object, so it would look like this:
<CodeExample classes={{ root: ..., button: ..., }} />
I'm adding this as a thought because it's not required to do anything now, just wanted to pose the question.
Might make sense as a FE V topic.
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 with you, but I see some components are already using the pattern elementClassName
so I just keep it for consistency but IMO, we should try to use the classes
prop to keep parity with MUIs API.
Co-authored-by: G r e y <grey@coder.com>
Demo:
https://user-images.githubusercontent.com/3165839/171438664-c599a10a-3261-4d9d-8042-5bec6c1281c6.mov
Closes #1926