3 ms·
Note that we're talking about an edge case for an authoring error - applying two conflicting styles to an element does not make sense, it has no defined behavio
by 9dev 2mo ago
Note that we're talking about an edge case for an authoring error - applying two conflicting styles to an element does not make sense, it has no defined behaviour, and is correctly flagged by linting tools as such.
Should Tailwind really go out of its way to pay a compile time tax, just to make this case resolve predictably? Or should people rather use code editors that point out invalid duplicated styles, which are always added in error?