A large portion of my game is written in TypeScript. For these portions of the game, I often use VSCodium to write it. However, there’s one aspect of auto-completion that is not working very well, and that is… bump-caps.
For some reason I can’t find any references of it by this name though I have a strong association of this feature with that name in my mind, but the idea of bump-caps is that when you’ve typed an upper-case letter, any candidate must also have an upper-case letter there. For example, ArrayList would be an OK candidate for AL, but Arraylist would be unacceptable because it does not have an upper-case L. Of course, you can have lower-case letters too – they are handy for disambiguation. For example, ArL would keep ArrayList in consideration while excluding e.g. ActiveLayer.
Today in VSCodium, I had an interface named HostGamepadRemovedEvent. I figured that by typing HGRE, I’d unambiguously select that type. But no. VSCodium decided that HTMLOptGroupElement is more likely, matching the R to the “r” in “group”. This is really annoying – and probably wouldn’t be too hard to fix, either.
I remember Eclipse, in contrast, did a great job with this when writing Java. I expect there would be many downsides to using Eclipse for TypeScript, though. I would be unsurprised if JetBrains has this down-pat.
Tags: Autocompletion, VSCodium