completeopt beaks stuff (best match not showing up)

[Kaikacy]

FAQ

• I have checked the FAQ and it didn't resolve my problem.

Announcement

• I have checked Breaking change announcement.

Minimal reproducible full config

cmp.setup {
    completion = {
        completeopt = 'menu,menuone,noinsert,preview'
    }
}

completeopt can have any value ( it still breaks )

Description

I've only noticed this on gdscript lps, but it's really annoying. when i set completeopt to anything first match of completion disappears after typing few letters, so if i am typing pos and it shows position as a first match, when i type next letter (i) that match just disappears and i have to trigger completions manually for it to show up again. and i want to have completeopt option set to preselect first item. I've set vim's completeopt option, but it only works for native autocompletion window. this might be related to gdscript lsp, because i haven't noticed this behavior on other language servers.

Steps to reproduce

with gdscript lsp setup in *.gd file try typing some keyword or function or whatever and once it finds the exact match, it just gets removed from the list of matches and completions needs to be manually triggered to show it again.

Expected behavior

display all the matches sorted from best to worst

Actual behavior

doesn't show the best match

Additional context

I'll try other completion engines and if it happens there too it's probably gdscript lsp's fault. but in that case what does cmp.completion.completeopt has to do with it?