-
Notifications
You must be signed in to change notification settings - Fork 218
No autocomplete of classnames in multi-folder workspace #692
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
Comments
Hey @ronaldtveen. Please can you share a reproduction? Ideally a GitHub repository where you already have everything all set up so we can clone it and immediately see the issue.
Yes, you can click the cog icon on the extension and select "Install Another Version...": |
I wish I could, it's a closed internal project which I cannot share. Let me see if I can spin up a new repro to reproduce it. I rolled back to |
Here you go; https://github.com/ronaldtveen/tailwind-issue This is my workspace file which works on
|
Thank you! Should be fixed in |
I stand corrected, I forgot to set up the settings key 😉 This now works!
Thanks a lot for the quick release @bradlc |
What do you see in the output panel? (you can run the |
Ahh, just edited my previous post haha. Thanks again! |
What version of Tailwind CSS IntelliSense are you using?
v0.9.3
What version of Tailwind CSS are you using?
v3.2.4
What package manager are you using?
npm
What operating system are you using?
macOS
Describe your issue
The following used to work until yesterday so I think it broke in
v0.9.2
.I'm working on a Vue project with Laravel as a PHP backend. Because I mostly work in Vue and not the PHP side of the project I use VSCode workspaces to split the project in parts; the root
/
as well as/resources/js/
for example.My
example.test.code-workspace
is as follows:When I open the project folder
example.test
in VScode then the autocomplete intellisense works perfectly fine. But when I open the workspace it does no longer autocomplete any classnames.PS Is there a way to rollback to a previous version?
The text was updated successfully, but these errors were encountered: