Skip to content

fix(eslint-plugin): [no-unnecessary-type-assertion] false positive on non-null assertion after an implicitly-any variable gets initialised inside conditional block #11082

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -118,9 +118,11 @@ export default createRule<Options, MessageIds>({
if (
// is it `const x!: number`
declaration.initializer == null &&
declaration.exclamationToken == null &&
declaration.type != null
declaration.exclamationToken == null
) {
if (declaration.type == null) {
return true;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We're definitely in the right ballpark, but I notice that this introduces a regression with the following case:

function foo() {
  let x
  if (Math.random() > 0.5) {
    x = 3;
  } else {
    x = 4;
  }
  // should be flagged as unnecessary
  x!;
}

I wonder if it's possible to get that case correct still? (it may or may not be feasible to prevent some false positives or negatives)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

actually - I think you can ignore this regression... This is most likely a symptom of #10334 / microsoft/TypeScript#60514

Copy link
Contributor Author

@mdm317 mdm317 Apr 18, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@kirkwaiblinger
Thanks for review! 🙏

The regression also occurs in this simplified case:

function foo() {
  let x;
  x =4;
  // should be flagged as unnecessary
  x!;
}

This is most likely a symptom of #10334 / microsoft/TypeScript#60514

As you mentioned, it's not possible to fix that case for now.

Should I close this PR until that issue is resolved?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmmm. I'm not sure which choice is the lesser of two evils here... fixing the bug at the cost of that rather undesirable-looking regression, or marking the bug as blocked. I'm gently leaning towards making this work as blocked unless we can find away to proceed while mitigating this regression 🤔 But then again if it was that important of a case, you'd think we might have a test case that caught it?

Looking for thoughts from @typescript-eslint/triage-team too.

}
// check if the defined variable type has changed since assignment
const declarationType = checker.getTypeFromTypeNode(declaration.type);
const type = getConstrainedTypeAtLocation(services, node);
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -429,6 +429,13 @@ declare function foo<T extends unknown>(bar: T): T;
const baz: unknown = {};
foo(baz!);
`,
`
let x;
if (Math.random() > -1) {
x = 2;
}
x!;
`,
],

invalid: [
Expand Down