mechanism to determine whether to add brackets { after attributes

[gennaro-tedesco]

We have been discussing a completion engine mechanism in this issue, where we would like to have a mechanism for blink.cmp to selectively decide whether or not to append brackets ({ or [) to texlab provided lsp completion items. From the discussion we have had it seems that blink.cmp logic checks for the completion kind of the relevant attributes and decides accordingly, however it seems that more often than not texlab returns attributes of type Function even when not so (see screenshot attached in the original issue).

Have you encountered a similar request already and how would you suggest to tackle the issue? I have browsed an almost similar issue here and have surfed the documentation a little but I could not find/understand whether the lsp already sends specifics for parentheses or not (thereby implying that a completion engine ought not execute any additional "bracket logic")?

TL;DR Does texlab provide a mechanism for completion engines to determine whether or not to add parentheses after completion attributes?

[Saghen]

Adding to this, many LSPs handle brackets themselves by defining the textEdit/insertText as a snippet and using a newText/insertText like function{$0}. On the completion engine side, we disable auto brackets for that LSP