Closed MichaelAllenWarner closed 1 year ago
To clarify: until very recently, this was working no matter how far into a file I was. And even now, everything else works just fine regardless of depth (autocomplete, color-squares); I think it's only the tooltip that's the problem.
Hey @MichaelAllenWarner, this was previously fixed in #846, and upgrading to the latest version of the extension (v0.10.0
) should resolve the issue 👍 (There may be a slight delay in this version being available.)
What version of VS Code are you using?
v1.81.1
What version of Tailwind CSS IntelliSense are you using?
v0.9.13
What version of Tailwind CSS are you using?
v3.3.3
What package manager are you using?
npm
What operating system are you using?
macOS
Tailwind config
(This isn't quite the full Tailwind config, for reasons that will become clear when you view the video below, but it's the substantial part of what you get by default with
create-next-app
.)VS Code settings
Reproduction URL
https://github.com/MichaelAllenWarner/tailwind-intellisense-config-file-demo
(I've included a setting in my
.vscode/settings.json
file that I think will make my experimental class-regex work for you if you view the Tailwind config file in VS Code, but I've also included my global VS Code settings above as requested.)Describe your issue
When using experimental class-regex, it seems that tooltips no longer work if there are at least 2001 characters in the file that precede the class. I'm not sure if that's the entirety of what's going on, but I'm seeing this sort of behavior. The video below shows what I mean, and maybe you can reproduce this behavior when you view the repo in VS Code.
I'd guess it might have something to do with this PR: https://github.com/tailwindlabs/tailwindcss-intellisense/pull/840
https://github.com/tailwindlabs/tailwindcss-intellisense/assets/44578578/efd413a8-2672-4caf-ad7d-b0228ff9a64d