Autocomplete jank when typing # typed: true

[jez]

Observed output

Screen.Recording.2024-04-15.at.3.45.40.PM.mov

Expected behavior

Sorbet should not delete what you've typed when you accept the autocomplete suggestion.

---

We’re like absolutely abusing the LSP completion interface for the purpose of showing that little “hey there! you’re need a # typed: sigil!” message

I have a feeling that if we make this say “you need to call resolve to resolve this completion item” we can make it do the right thing?

I think possibly this pushes the problem around, because I think it’ll mean that every keystroke in a # typed: false file will send a textDocument/completion request which might be orders of magnitude more requests than we get now, but maybe it doesn’t matter?