Microsoft/TypeScript

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

Open

#4,262 建立於 2015年8月10日

在 GitHub 查看
 (8 留言) (0 反應) (0 負責人)TypeScript (48,455 star) (6,726 fork)batch import
Help WantedSuggestion

描述

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.

貢獻者指南

技術棧
typescript
領域
developer experiencetooling
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
4
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
over 1 week
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
understanding of TypeScript compiler internals
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
15
研究方向
The issue describes a bug where typing a dot in a function parameter list triggers arbitrary completions instead of suggesting the splat operator (...). The TypeScript language service's completion logic in `src/services/completions.ts` likely handles this. Investigate the relevant code, especially the `getCompletionsAtPosition` function, and understand how completions are filtered for parameter contexts. Look for any existing tests related to parameter completions. Consider proposing a change that adds a completion entry for `...` when a dot is typed after a parameter name. Review the issue comments for any additional insights or constraints.