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
I see people face some issues with Stylelint while using Tailwindcss. Please either update the linter config to automatically ignore the errors related to Tailwindcss or let the programmer make such modifications or provide a better way to do this than adding some tweak to the code base to make the linter avoid the error.
I don't think it is a good idea to manipulate the codebase to prevent errors caused by the QA mechanism.
The text was updated successfully, but these errors were encountered:
Yes, I completely agree with @ahangarha points above, We(students) have been having some issues with using Tailwind CSS, and it would be great if support for tailwind CSS can be added to the config files
I see people face some issues with Stylelint while using Tailwindcss. Please either update the linter config to automatically ignore the errors related to Tailwindcss or let the programmer make such modifications or provide a better way to do this than adding some tweak to the code base to make the linter avoid the error.
I don't think it is a good idea to manipulate the codebase to prevent errors caused by the QA mechanism.
I see people face some issues with Stylelint while using Tailwindcss. Please either update the linter config to automatically ignore the errors related to Tailwindcss or let the programmer make such modifications or provide a better way to do this than adding some tweak to the code base to make the linter avoid the error.
I don't think it is a good idea to manipulate the codebase to prevent errors caused by the QA mechanism.
The text was updated successfully, but these errors were encountered: