Should not block completions when let a on the previous line

[zardoy]

Bug Report

🔎 Search Terms

no let variable completions suggestions

⏯ Playground Link

Playground link with relevant code

💻 Code

let superLongVariable

// No completions here

🙁 Actual behavior

No completions

🙂 Expected behavior

Should not block completions

Note: it is different from #54654 as it is not regression, TypeScript was always blocking it as I remember, but I do not understand why e.g. we can have something like this:

let superLongVariable
superLongVariable = 5

[MartinJohns]

but I do not understand why e.g. we can have something like this:

let superLongVariable
superLongVariable = 5

Because of ASI this is essentially:

let superLongVariable;
superLongVariable = 5;

And this is valid code.

[fatcerberus]

@MartinJohns I think that’s what OP meant - it is valid code, so TS should offer a completion for superLongVariable there, but doesn’t.

TypeScript was always blocking it as I remember, but I do not understand why [this is the case when] we can have something like this:

[RyanCavanaugh]

The problem is that you could be writing

let superLongVariable
= 4;

and we have logic that basically says if you're possibly about to write that =, we shouldn't offer completions.

Seems tweakable though

[fatcerberus]

Actually it looks like this does already work?

[gabritto]

Actually it looks like this does already work?

That looks like a "word completion", not a TS completion.

[svipas]

Same issue happens with this code:

const obj = {
  name: '',
} as const

// no completions of `obj`