[IntelliSense] Add a setting to force enable the IntelliSense extension

[AstragoDE]

Why should such a setting exist?

I recently started using Tailwind CSS in Nuxt using the Tailwind CSS Module. Due to this, I do not necessarily need to have a tailwind.config.js file or similar file, but in order for the plugin to activate, I would need one.
In addition, I would see that such a setting would be useful, if I want automatic completion, when I just use the Tailwind Play CDN.

Why should it be an extension setting and not something else?

Settings for extensions can be set for different levels, meaning that VS Code settings can be changed in a per-workspace or even per-folder manner, and not only globally (the global force enable setting would be disabled by default).

Changing a setting in the workspace section creates a .vscode folder in the project root / folder root with a file called settings.json, meaning that the workspace settings are saved in the project itself and therefore would be the same for other contributes.
The settings.json file could look like this to force enable IntelliSense:

{
  "tailwindCSS.forceEnableIntelliSense": true
}

In addition to the above-mentioned advantage, I believe that implementing a force enable setting using the VS Code settings could be easier to implement and operate, and would conform to an already existing standard for changing settings for a specific workspace.

---

Thank you very much for considering my idea for this feature.

[mybearworld]

As far as I can tell, the module uses TailwindCSS 2, you should probably not use it.

[AstragoDE]

Thank you for letting me know. I still think the above-mentioned feature should be implemented, since some people like to use the Play CDN.