fix(57348): Auto-complete on satisfies auto-imports satisfies

[a-tarasyuk]

Fixes #57348

[DanielRosenwasser]

Special-casing just these two feels off - why can't we just return both the auto-import and the keyword? For example, if you have a module like this:

namespace foo {
    export function await() {

    }
}

export = foo;

Both the keyword and auto-import are available in other files.

[a-tarasyuk]

As I understand it, this "special-casing" should apply in cases where the user is in a "casting/satisfies" position.

1 a/**/
1 sati/**/
// should we suggest auto-import here?

[DanielRosenwasser]

I suppose that's fine - in which case, at the very least that you need to check for no line terminator before the position, right?

[andrewbranch]

Isn’t the keyword supposed to be present and sorted above the auto-import? Here’s async, for example:

In a position like 1 satisf/**/, it’s true that an identifier would be invalid, so we could consider blocking all auto-imports there. However, I sometimes find myself wanting completions in the middle of a messy edit:

const x = someFn bla/**/, foo); // going to backtrack and add the missing `(`

so I’m hesitant to block completions based on relying too much on the current state of the parse tree. It feels to me like the bug is just that the keywords don’t show up here, even though they’re valid:

[a-tarasyuk]

[andrewbranch]

Thanks @a-tarasyuk!