I got a bit lazy and didn't take these into account and only use what's enabled/disabled in the config file. So for instance, when autocompletion is enabled in the config file but the server doesn't support it, autocompletion will not work - instead, it should fall back to the TM implementation.
Since the defaults will be enabled for most options, users would have to manually disable the features the given server doesn't support to get the TM fallback which isn't very user-friendly.
Example of such a initialize response from the server is for instance something like below. Currently only some of them are parsed and used, such as commit characters or text document sync kind.
I got a bit lazy and didn't take these into account and only use what's enabled/disabled in the config file. So for instance, when autocompletion is enabled in the config file but the server doesn't support it, autocompletion will not work - instead, it should fall back to the TM implementation.
Since the defaults will be
enabled
for most options, users would have to manually disable the features the given server doesn't support to get the TM fallback which isn't very user-friendly.Example of such a
initialize
response from the server is for instance something like below. Currently only some of them are parsed and used, such as commit characters or text document sync kind.