make code completions an experimental opt-in before the alpha release #74
Description
We could do something similar to what r-a does with their "experimental" capabilities which requires explicit opt-in from client side. Refer to the first paragraph in https://github.com/rust-lang/rust-analyzer/blob/master/docs/book/src/contributing/lsp-extensions.md#lsp-extensions:
All capabilities are enabled via the experimental field of
ClientCapabilitiesorServerCapabilities.
Specifically, here they send the capabilities that the VS Code extension supports.
So, for us it could look like below which would be sent when during the server initialization process:
"capabilities": {
"experimental": {
"completions": {
"enabled": true
}
}
} Originally posted by @dhruvmanila in astral-sh/ruff#17744 (comment)