@ts-nocheck seems to be ignored on TS file

[mjbvz]

From @arsnl on August 25, 2018 0:59

• VSCode Version: 1.26.1
• OS Version: macOS High Sierra 10.13.6
• TypeScript: 3.0.1

Steps to Reproduce

1. Add // @ts-nocheck at the start of any TypeScript file
2. Try to trigger any TS check error

Result

VS Code display TS error

Expected

VS Code should not display TS error

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

Snippet to try

// @ts-nocheck

const test = (foo: string) => `${foo}-bar`;

test(1); // Should not display error

test('baz'); // Correct behavior with correct type

// @ts-ignore
test(1); // Correct behavior with @ts-ignore

Copied from original issue: microsoft/vscode#57187

[weswigham]

In the original design (#14496) the intent was for ts-check and ts-nocheck to only have meaning in JS files. The same was true with ts-ignore. We gave in to community demands for ts-ignore in TS code; so I suppose this now tracks the same for ts-nocheck.

[hpmax00]

any update ？

[martpie]

@hpmax00 if you read the comment just before yours, you can see this is intentional and is not a bug.

From experience (I’ve been there), you would need it for TS files only when something is not correctly configured in your editor or your project, so I advice you to double check your config :)

[hpmax00]

@martpie My situation is not as simply as you said just configuring the ide. You said it is intentional. Good job, your house your rules. Anyway thank you for reply.

[doberkofler]

@martpie I would find this most helpful especially in the transition to TypeScript or is there another elegant way to prevent files from being type checked?