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 Reporduce repo
I am working custom element in plain JS project, and when i assign style to the html tag though class attributes, seem the checking was disabled.
To Reproduce
Steps to reproduce the behavior:
Go the repo provided
run npm install && npx eslint .
Expected behavior tailwindcss/no-custom-classname should be trigger
Screenshots
connectedCallback(){consttemplate=document.createElement('template');template.innerHTML=`<link rel="stylesheet" href="${mainCss}"><main class="page"> <section class="${clsx("xyz")}"> Use clsx wrapper the class naem to trigger eslint</section> <section class="page-content"> Useing wrong class names without error </section></main>`;this.shadowRoot.appendChild(template.content.cloneNode(true));}
Only the class wrapped in clsx has been checked.
Environment (please complete the following information):
OS: Mac
Softwares + version used:
Node 20
eslint-plugin-tailwindcss 3.17.5
eslint 9.13.0
Additional context
Add any other context about the problem here.
eslint config file or live demo
By providing a link to a live demo, a demo video or a github repo fixing the issue will be easier.
The text was updated successfully, but these errors were encountered:
Describe the bug
Reporduce repo
I am working custom element in plain JS project, and when i assign style to the html tag though
class
attributes, seem the checking was disabled.To Reproduce
Steps to reproduce the behavior:
Expected behavior
tailwindcss/no-custom-classname
should be triggerScreenshots
Only the class wrapped in clsx has been checked.
Environment (please complete the following information):
Additional context
Add any other context about the problem here.
eslint config file or live demo
By providing a link to a live demo, a demo video or a github repo fixing the issue will be easier.
The text was updated successfully, but these errors were encountered: