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.

Sign up for GitHub

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

Jump to bottom

[BUG] ring-opacity-N triggers tailwindcss/migration-from-tailwind-2 #351

Open
ivosabev opened this issue Jul 10, 2024 · 0 comments
Open

[BUG] ring-opacity-N triggers tailwindcss/migration-from-tailwind-2 #351

ivosabev opened this issue Jul 10, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@ivosabev
Copy link

Using ring-opacity-N triggers the migration rule that opacity should be in the format bg-opacity/50 instead of bg-opacity-50, which is not correct, because in TailwindCSS 2 the syntax for ring opacity has not changed.

https://v2.tailwindcss.com/docs/ring-opacity

I am using eslint-plugin-tailwindcss version 3.17.4.
@ivosabev ivosabev added the bug Something isn't working label Jul 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ivosabev