Skip to content

Project prefix feature is not working for class strategy #64

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

Closed
prgrssm opened this issue Mar 31, 2021 · 5 comments · Fixed by #91
Closed

Project prefix feature is not working for class strategy #64

prgrssm opened this issue Mar 31, 2021 · 5 comments · Fixed by #91
Assignees

Comments

@prgrssm
Copy link

prgrssm commented Mar 31, 2021

What version of @tailwindcss/forms are you using?

v0.3.1

What version of Node.js are you using?

v15.12.0

What browser are you using?

Chrome

What operating system are you using?

Windows

Reproduction repository

none

After adding prefix to tailwind config it's not applied to "class" strategy generated rules. Is it a bug?

RayoGundead added a commit to RayoGundead/tailwindcss-forms that referenced this issue Apr 9, 2021
Using the `class` strategy makes it work like a collection of form component styles and shouldn't be in the `base` layer.

Also addresses tailwindlabs#64.
@andreasnuesslein
Copy link

andreasnuesslein commented Dec 16, 2021

this is true for me for everything tailwind-related, not just tailwindcss-forms

@dextermb
Copy link

I've just ran into this issue as well. Damn

@andreasnuesslein
Copy link

andreasnuesslein commented Dec 20, 2021

I've just ran into this issue as well. Damn

for some reason I fixed it by just moving "vue" to the beginning of the content:
content: ["./src/**/*.{html,js,vue,ts}"] -> content: ["./src/**/*.{vue,html,js,ts}"]

@simonc
Copy link

simonc commented Jan 27, 2022

Hi there. Faced the same issue today. Another related aspect is that it's not respecting the important: true setting either it seems.

@RobinMalfait
Copy link
Member

Hey! Thank you for your bug report!
Much appreciated! 🙏

This has been fixed by #91 and will be available in the next release!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants