Replies: 3 comments 1 reply
-
hi check this mayb it fixes |
Beta Was this translation helpful? Give feedback.
-
Thank you for the reply. It seems my cssConflict was already enabled for 'everywhere'. I don't see the config but that is how it seems to behave. If I add the linked regex to my config, it seems to get the same results where duplicate CSS properties are identified in unrelated strings. |
Beta Was this translation helpful? Give feedback.
-
@cannap Thanks! This worked for me |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
What version of Tailwind CSS IntelliSense are you using?
What version of Tailwind CSS are you using?
What editor are you using?
Describe your issue
As shown in the screenshot example, tailwindcss-intellisense warns me about a cssConflict while the offending element className has no relation with the one used with twMerge.
Beta Was this translation helpful? Give feedback.
All reactions