user-provided custom LSP backends (a.k.a semantic completion)

[goranmoomin]

Currently TabNine only allows cquery for C/C++, flow for JS, typescript-language-server for TS, e.g.
However, cquery is unmaintained(clangd/ccls are competing in the space), flow only works (AFAIK) for flowjs code, the installation method npm used when installing flow, typescript-language-server, html-languageserver, ocaml-language-server, e.g. may not be preferred by users using yarn.

These kind of problems will persist as all computer environments are different, and (while providing good defaults are great)TabNine shouldn't decide a definite way to install/run LSP servers.

I would appreciate adding user-provided custom LSP backends.

[CarlQLange]

I think you may be incorrect. You can use different backends by configuring them like in this document (which has an example of ccls instead of cquery).

[goranmoomin]

@CarlQLange Oops; I should RTFM :-(

_{Sent with GitHawk}