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
Is your feature request related to a problem? Please describe.
I'm working on a project where I'm using Tailwind CSS, and I'd like to enforce a rule that limits the use of only specific Tailwind utility classes across the codebase. It would be beneficial to whitelist certain classes to ensure consistency and avoid the accidental use of unapproved or unnecessary classes. I often find it frustrating to track down and prevent classes that deviate from the design system or approved styles.
Describe the solution you'd like
I would like to see a new ESLint rule introduced that allows us to configure a whitelist of Tailwind classes that are permitted in the project. The rule would throw an error or warning if any non-whitelisted Tailwind class is used. This would help maintain consistency and enforce a strict design system by ensuring only approved Tailwind classes are used.
Describe alternatives you've considered
I’ve considered manual code reviews to spot and remove unapproved Tailwind classes, but this is time-consuming and prone to errors.
Additional context
I've implemented it by copying no-custom-classname and slightly adjusting the logic, I can prepare a PR if you would be interested.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I'm working on a project where I'm using Tailwind CSS, and I'd like to enforce a rule that limits the use of only specific Tailwind utility classes across the codebase. It would be beneficial to whitelist certain classes to ensure consistency and avoid the accidental use of unapproved or unnecessary classes. I often find it frustrating to track down and prevent classes that deviate from the design system or approved styles.
Describe the solution you'd like
I would like to see a new ESLint rule introduced that allows us to configure a whitelist of Tailwind classes that are permitted in the project. The rule would throw an error or warning if any non-whitelisted Tailwind class is used. This would help maintain consistency and enforce a strict design system by ensuring only approved Tailwind classes are used.
Describe alternatives you've considered
I’ve considered manual code reviews to spot and remove unapproved Tailwind classes, but this is time-consuming and prone to errors.
Additional context
I've implemented it by copying
no-custom-classname
and slightly adjusting the logic, I can prepare a PR if you would be interested.The text was updated successfully, but these errors were encountered: