IntelliSense in VS Code gives suggestions outside strings

[bradleyayers]

Describe the bug
When I type else { I get a suggestion {}-[], and when I press enter it's accepted and I end up with else {}-[].

To Reproduce
Steps to reproduce the behavior:

Create a .ts file with:

const response = await fetch(`https://raw.githubusercontent.com/foo/bar-baz/refs/heads/master/readme.txt`);

if (true) 

Then after the if (true) type {

Expected behavior
No auto complete

Screenshots

Desktop (please complete the following information):

• VS Code + Tailwind CSS IntelliSense extension

Additional context

I've tracked it down to the regex suggested in https://www.tailwind-variants.org/docs/getting-started

{
  "tailwindCSS.experimental.classRegex": [
    ["([\"'`][^\"'`]*.*?[\"'`])", "[\"'`]([^\"'`]*).*?[\"'`]"]
  ]
}

Instead I'm now using this (but it's too early to tell if it's good)

{
  "tailwindCSS.experimental.classRegex": [
    ["(`.*?`)", "(\".*?\")", "('.*?')"],
  ]
}

[iangrayhazzard]

Doesn't the suggested regex also start autocompleting tailwind classes inside any string in the document? I'd suggest we make it tv() specific, like clsx and cva:

["tv\\(([^)]*)\\)", "(?:'|\"|`)([^']*)(?:'|\"|`)"]

[EthanBarlo]

This seems to work best for me.
First it limits the scope within the tv({}) object,
Then it will give IntelliSense to any quoted ("", '', ``) string within that object.

"tailwindCSS.experimental.classRegex": [
   ["tv\\(\\{([\\s\\S]*?)\\}\\)", "['\"`]([^'\"`]*)['\"`]"]
]

Since we're scoping it to the tv({}) object it means nothing else within the project should have random IntelliSense.