I have the same issue with that package. Everything works fine and catches the errors ok, but autocomplete does not seem to work. I also added a config.nims to my working directory with:
switch("define", "ssl") switch("threads", "on") switch("define", "release")
This helps with the SslError highlighting in VSC. In my case, my best guess is that it is running nimsuggest and nim from the /usr/bin directory and not the nimble directory. I haven't found direct documentation (and I've been to lazy to scour the forum to see if any kind soul already went through this and documented it). I use debian and the version it installs by default cannot install the telebot code from nimble, but when you use the nimble directory and compile it using the ~/.nimble7bin/nim then it works just fine. I looked at my ps output searching for nimsuggest while running VSC:
localho+ 305032 0.7 0.5 300028 191332 ? Sl 10:35 0:02 /usr/bin/nimsuggest --epc --v2 TELEG.nim
as you can see it is running the nimsuggest version in /usr/bin, which defaults to the version in apt: Nim Compiler Version 1.4.2 [Linux: amd64]
whereas my nimsuggest in ~/.nimble/bin is Nim Compiler Version 1.7.1 [Linux: amd64]
I think it's just a question of binding or exporting working directories. I just haven't gotten around to reading about it and trying it out. Also, the telebot code is so wonderful that reading it is like going through melting butter in a pan. Shoutout to the dev and contributors for their awesome work!
Hope someone who's run into this in the past (and was able to work around it) can give me a clue? I don't know if this is the case with you EntryName, but I hope this helps you (or anyone) :)