-
Notifications
You must be signed in to change notification settings - Fork 19
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
Pseudo-Classes and the Theme Specification #11
Comments
In as far as the Theme UI implementation goes and sort of implied by this spec, defining pseudoclasses in variants is absolutely possible. E.g.: {
buttons: {
primary: {
color: 'background',
bg: 'primary',
':hover': {
bg: 'secondary',
}
}
}
} |
@jxnblk Thank you for this response! Is this documented anywhere? I've been using various tools in this little "family" for a couple months now, and it's not really clear that this is possible or what the syntax to do it is. |
Emotion documents this, but this seems like a gap in our current documentation. I'm working on some updates that should make this more clear in the https://theme-ui.com/sx-prop/ docs, so thanks for bringing this up! |
Hey, just picking up theme-ui -- couldn't see any mention of it in your docs still. Am I mistaken? |
I don't know about a year ago, but as of 2022-05-30, there's a mention on that Though I think it could use its own section. I got here looking for support for the |
Just want to start out by saying thank you for developing this, as it's made my life much easier as a developer.
I'm wondering if there is current, undocumented functionality for pseudo-classes or if plans exist to implement this?
For example:
Without this ability, the variants feature really loses a lot of its usefulness, since I can't entirely define variant styles inside the theme and have them "just work". Instead, I have to do something like:
background: ${({ theme, variant }) => theme.buttons[variant].hoverBg}
for all of my styles.Hopefully this makes sense. I'm still figuring out how to use this theme spec and styled-system to their fullest, so let me know if I am missing something!
The text was updated successfully, but these errors were encountered: