Skip to content

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

Closed
ronaldtveen opened this issue Jan 5, 2023 · 7 comments
Closed

No autocomplete of classnames in multi-folder workspace #692

ronaldtveen opened this issue Jan 5, 2023 · 7 comments
Assignees

Comments

@ronaldtveen
Copy link

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:

{
  "folders": [
        { "path": "../Sites/example.test" },
        { "path": "../Sites/example.test/resources" },
        { "path": "../Sites/example.test/resources/js/Components" }
    ],
    "settings": {
        "tailwindCSS.experimental.configFile": "../Sites/example.test/tailwind.config.js"
    }
}

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?

@bradlc
Copy link
Contributor

bradlc commented Jan 5, 2023

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.

PS Is there a way to rollback to a previous version?

Yes, you can click the cog icon on the extension and select "Install Another Version...":

CleanShot 2023-01-05 at 14 05 17@2x

@ronaldtveen
Copy link
Author

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 v0.9.1 and then it works again, but installing v0.9.2 breaks it.

@ronaldtveen
Copy link
Author

ronaldtveen commented Jan 5, 2023

Here you go; https://github.com/ronaldtveen/tailwind-issue

This is my workspace file which works on v0.9.1 and does not on v0.9.2

{
  "folders": [
    { "name": "tailwind-issue.test", "path": "../Sites/tailwind-issue.test" },
    { "name": "Pages", "path": "../Sites/tailwind-issue.test/resources/js/Pages" },
    { "name": "Components", "path": "../Sites/tailwind-issue.test/resources/js/Components" }
],
  "settings": {}
}

@bradlc bradlc self-assigned this Jan 5, 2023
@bradlc
Copy link
Contributor

bradlc commented Jan 5, 2023

Thank you! Should be fixed in v0.9.4 via #693 but let me know if you're still having issues 👍

@bradlc bradlc closed this as completed Jan 5, 2023
@ronaldtveen
Copy link
Author

ronaldtveen commented Jan 5, 2023

Just installed v0.9.4 and reloaded VSCode but no such luck for me it seems?

I stand corrected, I forgot to set up the settings key 😉 This now works!

{
  "folders": [
    { "name": "tailwind-issue.test", "path": "../Sites/tailwind-issue.test" },
    { "name": "Pages", "path": "../Sites/tailwind-issue.test/resources/js/Pages" },
    { "name": "Components", "path": "../Sites/tailwind-issue.test/resources/js/Components" }
  ],
  "settings": {
    "tailwindCSS.experimental.configFile": "../Sites/tailwind-issue.test/tailwind.config.js"
  },
}

Thanks a lot for the quick release @bradlc

@bradlc
Copy link
Contributor

bradlc commented Jan 5, 2023

What do you see in the output panel? (you can run the Tailwind CSS: Show Output command to reveal)

@ronaldtveen
Copy link
Author

Ahh, just edited my previous post haha. Thanks again!

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

No branches or pull requests

2 participants