[IntelliSense] Show which class is winning when there is a conflict

[skttl]

When I have two classes conflicting, in would be good to know which one wins.

In this example, the div would be display:flex, so if there could be some kind of message saying that, that would be nice!

Especially when you are cleaning up old code from a developer who doesn't have linting, and you just want to remove the classes being disregarded.

[rozsazoltan]

This depends on the order of classes in the generated CSS. It's completely random that .flex { ... } gets added after .block { ... } in generated CSS. There's no point in looking for a "winner" (when they have same specificity); the incorrect usage case should simply be avoided.

The current warning is perfect for this; remove the one you added incorrectly.

[skttl]

Are you sure the order is completely random? In tailwind 3 the order was always the same (at least on a fresh build)

[skttl]

There's no point in looking for a "winner" (when they have same specificity)

When the specifity is the same, the last definition wins.

Eg.

.flex {
display:flex;
}

.block {
display:block;
}

In this case block trumps flex

[skttl]

The current warning is perfect for this; remove the one you added incorrectly.

I didn't add it, I'm trying to clean up unlinted code that "works"

[skttl]

I know its inconsistent :)

But in this usecase, I'm taking over a codebase, where the client thinks it "works", or in other words - the website looks as it should. So I just want to remove the class that is not applied, to make the linter happy.

I could open up the page in a browser and verify which one is disregarded, but it would much faster if the linter could just tell me.

[rozsazoltan]

Are you sure the order is completely random?

A-a. That's not what I meant, but never mind.

• sort.ts

It just seems absurd to me to remove the currently non-applicable utility solely based on this, without any verification, especially when it's not certain that it's actually design is correctly. (Although I agree, if the client thinks so, then you really only want to remove the unused utilities. I understand.)

And I get it - this is what you would do right now if you needed this information. You're not asking for the impossible; I just like to engage with critique to make sure this is really necessary.

[rozsazoltan]

In this case, I would add an extra warning to the non-applicable utility, making it clear that for some reason it won't take effect. I'm not sure if it's possible, but maybe you could make the utility's text color slightly transparent - it would provide a clearer indication that it's not in use.

[skttl]

Thats pretty much what I want :)