Bug: [ban-ts-comment] false positive when @ts-nocheck is not at the beginning of the file

[auvred]

Before You File a Bug Report Please Confirm You Have Done The Following...

• I have tried restarting my IDE and the issue persists.
• I have updated to the latest version of the packages.
• I have searched for related issues and found none that matched my issue.
• I have read the FAQ and my problem is not listed.

Playground Link

https://typescript-eslint.io/play/#ts=5.4.2&fileType=.ts&code=FBA&eslintrc=N4KABGBEBOCuA2BTAzpAXGUEKQAIBcBPABxQGNoBLY-AWhXkoDt8B6AIwEMnb9layAewC2wxC3RRE0aIOiRwYAL4glQA&tsconfig=&tokens=false

Repro Code

const a = 1

// @ts-nocheck - should not be reported

// TS error is not actually suppressed
const b: string = a

ESLint Config

module.exports = {
  parser: "@typescript-eslint/parser",
  rules: {
    "@typescript-eslint/ban-ts-comment": "error"
  }
};

tsconfig

{
  "compilerOptions": {
    // ...
  }
}

Expected Result

// @ts-nocheck should not be reported because valid TS pragmas should be placed at the beginning of the file

Actual Result

// @ts-nocheck and // @ts-check are reported even if they are not valid TS pragmas

Additional Info

Follow up for #8416

[bradzacher]

I'm not sure I agree - what's the problem with reporting it anywhere?
The user intent was clear even if it didn't work.

Is there a usecase for keeping these comments?

[auvred]

Is there a usecase for keeping these comments?

I don't think so :)

My intention was to be completely consistent with TypeScript's handling of directive comments.

Since after #8416, the following cases are no longer reported:

/* @ts-nocheck */
/** @ts-nocheck */
///// @ts-nocheck

So I thought it would be nice to fix the last inconsistency with TS behavior - reporting on misplaced @ts-nocheck comments!