Setting to Disable .js / .ts Autocomplete?

[karlhorky]

Hi @vunguyentuan 👋 hope you are well :)

Would you consider adding a setting to disable the .js / .ts autocomplete feature for projects that do not use CSS-in-JS?

Currently, in a project that does not use CSS-in-JS, the extension fills the autocomplete entries all over the place in JS, JSX, TS and TSX files with useless entries for CSS variables:

For example, adding a new setting called cssVariables.autocompleteInLanguages, default values below:

{
  "cssVariables.autocompleteInLanguages": [
    "css",
    "less",
    "scss",
    "postcss",
    "javascript",
    "javascriptreact",
    "typescriptreact"
  ],
}

Or, if this is based on file extension instead of language in the file, a new setting called cssVariables.autocompleteInFiles, default values:

{
  "cssVariables.autocompleteInFiles": [
    "*.css",
    "*.scss",
    "*.sass",
    "*.less",
    "*.js",
    "*.jsx",
    "*.ts",
    "*.tsx"
  ]
}

[Cellule]

👍 I do not use styles in javascript and the autocomplete is just pollution. I really only want them in css files.
It's fine if that's the default, but I was expecting a setting

[karlhorky]

@Cellule @vunguyentuan thanks for the setting!

[karlhorky]

@vunguyentuan is this new cssVariables.languages setting working completely?

I'm still receiving suggestings in a .ts files (typescript syntax), even though I have disabled those:

Disabling the extensions makes these suggestions disappear.

This is my settings configuration:

{
  "cssVariables.languages": [
    // "astro",
    // "svelte",
    // "vue",
    // "vue-html",
    // "vue-postcss",
    "scss",
    "postcss",
    "less",
    "css",
    "html",
    // "javascript",
    // "javascriptreact",
    // "typescript",
    // "typescriptreact",
    "source.css.styled"
  ]
}

[Cellule]

I admit something is off. It worked fine initially with my fork, then once it was published it no longer seemed to work
Haven't had time yet to investigate

[karlhorky]

@vunguyentuan can we reopen this issue?

[Cellule]

@karlhorky I found my bug 😅
#85
Sorry about that, hopefully it gets merged and released soon :)

[karlhorky]

Amazing, thanks! Watching #85 now :)

[karlhorky]

@vunguyentuan @Cellule thanks for the PR and merge!

I can confirm that this is fixed in the new 2.7.1 version which was just published 🙌