`defaultVariants` should be ignored by Tailwind IntelliSense

[petvi]

I noticed defaultVariants properties are being intellisensed by the TailwindCSS IntelliSense Extension when using the settings snippet provided in the docs:

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

These properties already have the TS types inferred correctly, so I think the RegEx simply needs to be updated to ignore this property.

[lauritzsh]

I assume related but also happens for responsiveVariants when I do

  {
    responsiveVariants: ['sm', 'md', 'lg'],
  }

We only have three screens so I do this hack for now to silence the warning

@layer base {
  .sm, .md, .lg {}
}

[its-monotype]

Should be closed by this: francoismassart/eslint-plugin-tailwindcss#232

[mskelton]

This is not really feasible given how the Tailwind intellisense extension works, it's basically all or nothing. Even if we constructed a regex that solved it for defaultVariants or responsiveVariants, other places would still inappropriately provide intellisense such as variant/slot names in compoundSlots or compoundVariants.

Closing as not planned.

[katerlouis]

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

These properties already have the TS types inferred correctly, so I think the RegEx simply needs to be updated to ignore this property.

How comes the docs have promoted a new regex as of this writing? https://www.tailwind-variants.org/docs/getting-started#intellisense-setup-optional

I find the current proposal far too aggressive as now every string gets intellisensed by tailwind.