Description
List of follow-up items from #46370 that were easier to put in separate PR(s). I tried to sort these by priority order, and the last couple I don’t think we’ll schedule at all for now. We can close this issue when we’ve done everything worth scheduling for a milestone.
-
Add$0
tabstop at the same location as$1
tabstop (in method body) -
Make auto-imported types work
- Moderate effort
- Sending this back as part of
getCompletionsAtPosition
would require a protocol change and corresponding update in typescript-language-features. There are some workarounds we could implement by sending the back as part ofgetCompletionEntryDetails
instead, which would work with no VS Code update. Maybe we should discuss this at next week's editor sync. My feeling is this qualifies as a bug fix, but if we need a VS Code update, we’ll need to coordinate with @mjbvz, and we’re also nearing the end of our own release cycle, so I’m not sure what the best strategy is here.
-
From @amcasey at Add method signature completions #46370 (comment):
public
must precedeabstract
.- Maybe 4.6?
-
From @amcasey at Add method signature completions #46370 (comment):
if you name the method to be overridden "abstract", "async", etc, the completion clobbers the keyword completion. It did this before the change too, but then it would insert the same text either way - now it inserts a whole function declaration.
- This can be backlog / help wanted / when you have time for it.
-
Improve
addMissingMember
codefix’s generated implementation signature for overloads (currently all parameters areunknown
(as of feat(47281): Implementing an interface suggests any as type #47308))- Let's listen for feedback about this. Unless you feel strongly about it or we hear a lot of complaints, I think this can be backlog / help wanted.