-
-
Notifications
You must be signed in to change notification settings - Fork 37
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
Missing support for stacking pseudo classes #368
Comments
Honestly, I do not know how to support this feature + it would generate a huge number of classnames types that the TS engine could not handle, that's why support for opacity suffix feature was also dropped |
Ah, that makes sense. Is there any kind of escape hatch helper so that I could still use classes like |
yes, you can cast the string to backgroundColor('bg-gray-100', 'active:hover:bg-gray-200' as TTailwindString) |
How would one do that in the case of conditionals?
I spose? I'll write my own helper probably for this case. Thanks for your help! |
also p.s. thanks for building this, i'm finding it super helpful. 💚 |
Environment:
TailwindCSS
version: ^3.0.15tailwindcss-classnames
version: ^3.0.2Node.js
version: 14.17Current Behavior
Using a multiple pseudo classes together throws a type error.
In this case, I attempted to combine
hover:…
andactive:…
.Expected Behavior
I should be able to stack pseudo classes in this way with no type-errors.
The text was updated successfully, but these errors were encountered: