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

Wrong styles displaying when multiple configs are in the webroot (since v0.12) #1027

Open
wpinfusion opened this issue Jul 30, 2024 · 0 comments
Assignees

Comments

@wpinfusion
Copy link

What version of VS Code are you using?

v1.91.1

What version of Tailwind CSS IntelliSense are you using?

v0.12.5

What version of Tailwind CSS are you using?

v3.4.1

What package manager are you using?

npm

What operating system are you using?

Manjaro Linux

Describe your issue

I have an issue that started since v0.12 of this extension. On v0.10.5 everything is fine.

I use TailwindCSS in a custom WordPress theme. This theme also has a child theme. Both are inside separate directories, and so are the tailwind.conf files. Imagine a directory tree like so:

.
├── parent/
│   ├── tailwind/
│   │   └── tailwind.conf
│   └── parent-theme/
│       └── index.php
└── child/
    ├── tailwind-child/
    │   └── tailwind.conf
    └── child-theme/
        └── index.php

In vscode the root of the project is opened, so both themes are in the scope. The issue is that when I use v0.12 or higher, and I work in the parent theme, the styles of the child theme appear in the dropdown. For example, when I type text- and the dropdown with colors appears, I only see the child theme's colors. To be clear - the parent colors, as defined in the config, do not appear in the dropdown.

The colors still work when I type them in manually. They get compiled, and display just fine on the front-end. It's purely TW Intellisense not detecting them.

I have reverted to v0.10.5 for the time being, since this is kind of important to me.

@thecrypticace thecrypticace self-assigned this Aug 2, 2024
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