-
Notifications
You must be signed in to change notification settings - Fork 10
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
Does not work when encounters variants classes #62
Comments
Can you make sure you're on the latest version (2.0.1) in your IDE? Also, can you give me a sample file that it's failing to work with? When testing against the latest release, it appears to move the variant to the beginning of the main variants area. Per play.tailwindcss.com - it should be in the back. I can definitely fix this, but I am curious to check in on the fact it stops formatting entirely first. Expected :flex min-h-full items-end justify-center p-4 text-center sm:items-center sm:p-0 [.peer:checked~&>.material-icons]:opacity-100
Actual :flex min-h-full items-end justify-center p-4 text-center [.peer:checked~&>.material-icons]:opacity-100 sm:items-center sm:p-0 |
Could be related to #63 actually. Let me know if you have issues after that goes out. |
this is now on the fix/arbitrary-variants branch - pending more testing to make sure the behaviors all make sense. |
I confirm that the issue is still present in v2.0.2. |
I ended up rewriting the variant handling here: #64 This file shows the output and the test is passing: and the tests pass in the GH action. The last thing I'm going to do is bring in more complicated examples. I'll make some over in play.tailwindcss.com and shuffle the classes around and make sure its all 100% before I ship it out. I cant possibly guess every configuration people will use, but I'm going to really try to get most of them. Edit: let me know if this still happens ? |
assuming we gucci - gonna close this. |
[.peer:checked~&>.material-icons]:opacity-100
is a perfect valid tailwind class (see arbitrary variants ), but when the plugin encounters this kind of classes, it refuses to format the whole element. Removing this class allow the plugin to format the element's classes.No log lines appear exept the default one :
2023-02-07 11:30:53,345 [127201544] INFO - #TailwindUtility - Loading default class order
The text was updated successfully, but these errors were encountered: