You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While you are more likely to change your styles mobile first and scale up, meaning mobile -> small -> large it would make sense to sort them this way as well, is it possible to make this an opt-in rule?
The text was updated successfully, but these errors were encountered:
Update: I just noticed the official sorting does go from small to large, since improved only mentions "Same as official but also sorts by data-attributes" I didn't try it at first
Update: I just noticed the official sorting does go from small to large, since improved only mentions "Same as official but also sorts by data-attributes" I didn't try it at first
I have noticed that the official order does not treat variants/modifiers differently than the normal classes. So they sometimes got mixed up in the order.
I think there should be more nuanced ways to sort tailwind classes that the current options don't provide, so I will definitely look into this in the future.
It seems like you are sorting multiline breakpoints from
none (mobile) -> large -> small
, i.e.:While you are more likely to change your styles mobile first and scale up, meaning
mobile -> small -> large
it would make sense to sort them this way as well, is it possible to make this an opt-in rule?The text was updated successfully, but these errors were encountered: