You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you are @mjbvz, please consider reading this bug report before closing the ticket with an irrelevant answer. The steps to reproduce take 60 seconds to complete.
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:
Launch with code --disable-extensions
Open User Settings and configure it as per below.
Create a new file
Type import test from "path"
Change the Language Mode to "JavaScript"
Hover over the word test and observe the message `[ts] 'test' is declared but its value is never read' appears inside the tooltip.
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
Important Clarification Default JavaScript settings should not be modified.
# 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
The text was updated successfully, but these errors were encountered:
If you are @mjbvz, please consider reading this bug report before closing the ticket with an irrelevant answer. The steps to reproduce take 60 seconds to complete.
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.
Steps to Reproduce:
code --disable-extensions
import test from "path"
test
and observe the message `[ts] 'test' is declared but its value is never read' appears inside the tooltip.User Settings for Step 2
Important Clarification Default JavaScript settings should not be modified.
Does this issue occur when all extensions are disabled?: Yes
The text was updated successfully, but these errors were encountered: