VSCode continues to display TypeScript errors when all TypeScript settings are disabled.

[dzrw]

We do not use TypeScript in several of our projects, so we have attempted to disable TypeScript validation in our JavaScript files. However, VSCode displays TypeScript-related messages despite the settings instructing it not to do so.

Apparently this is a regression in the latest build because there was another long bug closed by @sandy081 about a similar issue back in March 2018 where the team appeared to have communicated that the ability to disable TypeScript was a feature that VScode supported.

• VSCode Version: 1.25.1
• OS Version: macOS 10.13.6

Steps to Reproduce:

1. Launch with code --disable-extensions
2. Open User Settings and configure it as per below.
3. Create a new file
4. Type import test from "path"
5. Change the Language Mode to "JavaScript"
6. Hover over the word test and observe the message `[ts] 'test' is declared but its value is never read' appears inside the tooltip.
7. The expected behavior is that VSCode does not attempt to communicate TypeScript-related error messages when TypeScript validation is disabled.

User Settings for Step 2

    # Surely one of these will turn off all [ts] messages in tooltips!
    "typescript.validate.enable": false,
    "typescript.autoImportSuggestions.enabled": false,
    "typescript.check.npmIsInstalled": false,
    "typescript.format.enable": false,
    "typescript.format.insertSpaceAfterCommaDelimiter": false,
    "typescript.format.insertSpaceAfterFunctionKeywordForAnonymousFunctions": false,
    "typescript.format.insertSpaceAfterKeywordsInControlFlowStatements": false,
    "typescript.format.insertSpaceAfterOpeningAndBeforeClosingNonemptyBraces": false,
    "typescript.format.insertSpaceAfterSemicolonInForStatements": false,
    "typescript.format.insertSpaceBeforeAndAfterBinaryOperators": false,
    "typescript.quickSuggestionsForPaths": false,
    "typescript.reportStyleChecksAsWarnings": false,
    "typescript.showUnused": false,
    "typescript.suggestionActions.enabled": false,
    "typescript.tsc.autoDetect": "off",
    "typescript.updateImportsOnFileMove.enabled": "never",
    "tslint.enable": false

Does this issue occur when all extensions are disabled?: Yes

[vscodebot]

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

• Unable to start VSCode 1.19.3 in X2go (#42619)
• Parameter hints do not disappear (#50467)
• Tab Drag and Drop between editors is CPU intensive (#28441)

[mjbvz]

Set the javascript version of this setting instead:

    "javascript.showUnused": false,

If you are in js files, use the javascript versions of those settings if they exist

[dzrw]

@mjbvz No, that's not the fix. I work in JavaScript, and I would like JavaScript-related error messages. Did you read the bug report?

[mjbvz]

Yes. The TypeScript extension powers our javascript intellisense which is why you see [TS] in your js file. That only indicates what extension is providing that error

[dzrw]

How does VSCode disambiguate TypeScript validations from JavaScript validations in the UX?

[mjbvz]

That's where the two versions of the settings come in: the typescript.* setting apply to typescript files specifically, while the javascript.* settings apply to javascript files. Behind the scenes both are powered by the typescript extension

[dzrw]

Thank you, that's an explanation that I can bring back to the team and not have folks scratching their heads.

[ajelcocks]

I have spent several days trying to stop a tooltip prefixed with [ts] and now I find it is not a TypeScript error? I have been pulling my hair out scouring the web, setting every possible setting to false, rebuilding projects and workspaces.

Two days of frustration and wasted effort...because the IDE tells me a JavaScript message using a TypeScript prefix/indicator.

That is just awesome! Thank you so much.

Perhaps you could look into maybe making it a little less confusing and putting a different [prefix] there, like oh I don't know ..[js] or something similar?