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
Describe the bug
A colleague of mine discovered this issue. We use the ESlint plugin at work and have a shared component library using a tailwind with a prefix to avoid collisions with other tailwind projects. While developing a new feature, we wanted to use the recently introduced syntax for named groups, but ESlint kept nagging about a non-existent class.
I looked into the code for no-custom-classname, and the regex responsible doesn't include the prefix from the tailwind config. I believe this is the issue.
Describe the bug
A colleague of mine discovered this issue. We use the ESlint plugin at work and have a shared component library using a tailwind with a prefix to avoid collisions with other tailwind projects. While developing a new feature, we wanted to use the recently introduced syntax for named groups, but ESlint kept nagging about a non-existent class.
I looked into the code for
no-custom-classname
, and the regex responsible doesn't include the prefix from the tailwind config. I believe this is the issue.To Reproduce
The plugin will report a false positive unknown class name
tw-group/edit
andgroup-hover/edit:tw-text-red-500
Expected behavior
Support the specified prefix specified inside the
tailwind.config.js
together with the named groups and peer syntax.The text was updated successfully, but these errors were encountered: