You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment when none of the contributed completion processors returns any proposals, the textual completion processor starts adding proposals.
That's fine for languages where we have no sophisticated completion processor, but looks bad for languages that pretend to have a 'smart' completion processor.
The text was updated successfully, but these errors were encountered:
That's fine for languages where we have no sophisticated completion processor, but looks bad for languages that pretend to have a 'smart' completion processor.
Well, I love it in TypeScript even tho it's smart. Textual completion proposes variable names, completes in comments and in strings, etc. Such a flag should only be used when having great confidence, like in member completion.
One option will be to add a isComplete flag to the CompletionList tho that's a big hammer. I can image some smart extension wanting to add quick fixes as completion proposals - like add method when doing unsuccessful member completion. We have to make sure we don't disable such scenarios with such a hammer.
At the moment when none of the contributed completion processors returns any proposals, the textual completion processor starts adding proposals.
That's fine for languages where we have no sophisticated completion processor, but looks bad for languages that pretend to have a 'smart' completion processor.
The text was updated successfully, but these errors were encountered: