Getting completions when writing out a dot in a parameter should suggest the splat operator

[weswigham]

At present the completions returned seem arbitrary. Example:

function(arg: string, ./**/): any {
}

Getting completions at the marker yields the typical alphabetical list of global things - worse yet, in VSCode, pressing . again auto-completes the first one (.AbstractWorker. isn't really a valid argument name)! Very frustrating.

[mhegazy]

This should be fixed in master. can you update your VSCode with latest tsserve.js and try again?

[mhegazy]

See #3242 for the original issue.

[weswigham]

It no longer yields a list of completions, but I'd still suggest that the splat operator itself be on the suggestion list. We offer completions for the get keyword, why not the ... operator?

[weswigham]

Similarly, when doing an assignment we no longer offer any completions while typing out the splat operator; why not suggest the splat operator itself?

[mhegazy]

but that is the same as other punctuation tokens..

[weswigham]

What do you mean the same as other punctuation tokens? I see no reason why TS couldn't offer completions for operators consisting of punctuation?

The splat is the only 3-character punctuation token and thereby the only one you can actually save a keypress by using completions to write it. I can't think of a situation where you type a . at the start of a statement (with no LHS to the dot) and don't want to write out ....

I also wouldn't mind having completions for => {} (and =>), too. >.>

[mhegazy]

is there a precedence in other tools\languages? i find it strange to find "==" and ">" in my completion list after "=".

[weswigham]

Operators are just infix functions which happen to be made up of punctuation. (Well, in Haskell anyway. In JS we have way less control over our symbols and no way to define custom operators.)

I don't know of any widely used editor which supports operator completions (yet) - when it comes to completions, VS is usually the go-to reference. I suppose in my mind I don't see why not to support them - it's a sequence of characters which the editor can reliably predict you'll want to use in certain places as indicated by the first character. Plus, adding operators to the completions list makes the live documentation of the features the language supports more complete. (For example, If I'm new to JS and I open my editor for the first time and I type = and see =, ==, and === as valid options and an explanation of what each is in the documentation, I'm being informed about what they are before I make any mistakes with them. As an added bonus, in TS we get to explain how the types flow through the operators in this kind of documentation - for example the curious type of the expression 2 || 'foo' (which despite always returning a number is of type number | string).)