You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Intellisense doesn't work when I apply the tailwind classes in the "styles" property of the decorator, nor in the "host" property, but it does work in the "template" property.
The text was updated successfully, but these errors were encountered:
Our "Tailwind CSS" language mode operates on entire files. It doesn't pick up arbitrary strings / template literals and treat them as a different language.
The rest of the language server that picks up on @apply stuff is detected and handled in <style> tags in HTML but, like above, not in arbitrary strings.
I unfortunately do not have a good workaround for this as things aren't currently architected in a way that makes one feasible (yet).
I'm gonna close this one for now but I would definitely like to improve this in the future. I don't have a timeline for it but if / when it does happen it will require the use of a tagged template literal to denote which part of the document is CSS.
Aside: When using IntelliSense for v4 we require the use of a CSS file to initialize a project. I'd recommend authoring stuff using the global stylesheet and just classes in the templates to get the best experience instead of using the styles property on a per-component basis if at all possible.
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.4
What package manager are you using?
npm
What operating system are you using?
Windows
Tailwind config
VS Code settings
Reproduction URL
Just generate a standalone component and attempt to apply some styles in the component's decorator.
Describe your issue
Intellisense doesn't work when I apply the tailwind classes in the "styles" property of the decorator, nor in the "host" property, but it does work in the "template" property.
The text was updated successfully, but these errors were encountered: