Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] border-opacity-* triggers "not a tailwind css class!" #108 #111

Closed
harryduong91 opened this issue Jan 27, 2022 · 4 comments
Closed
Labels
bug Something isn't working

Comments

@harryduong91
Copy link

Describe the bug
border-opacity-10(0-100) triggers eslint no-custom-classname rules.

To Reproduce
Steps to reproduce the behavior:

  1. Go to any div
  2. Add className with border-opacity-*
  3. See warning

Expected behavior
Should not show warning

Screenshots
image

Environment (please complete the following information):

  • OS: macOS
  • Softwares + version used:
    • VSCode 1.63.2
    • Tailwind 3.0.12
    • eslint-plugin-tailwindcss ^3.3.5
@harryduong91 harryduong91 added the bug Something isn't working label Jan 27, 2022
@francoismassart
Copy link
Owner

Hi @harryduong91
This is not a bug, this is on purpose see this comment on similar issue with its possible actions
#108 (comment)

@francoismassart
Copy link
Owner

Don’t hesitate if you need more infos or if you have questions 😉

@harryduong91
Copy link
Author

Got it. Thanks @francoismassart

francoismassart added a commit that referenced this issue Jan 27, 2022
@francoismassart
Copy link
Owner

@harryduong91 in fact, I was wrong, there was something to fix in here.

border-opacity-* should not trigger no-custom-classname rule but trigger instead migration-from-tailwind-2.

I just fixed it in [email protected], it was released few minutes ago.

Thank you for bringing the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants