Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | refactor(lsp): resolve the config-client entanglement | Lewis Russell | 2024-02-13 |
| | | | | | | | | | | | | | | | | | | | | | Previously the LSP-Client object contained some fields that are also in the client config, but for a lot of other fields, the config was used directly making the two objects vaguely entangled with either not having a clear role. Now the config object is treated purely as config (read-only) from the client, and any fields the client needs from the config are now copied in as additional fields. This means: - the config object is no longet normalised and is left as the user provided it. - the client only reads the config on creation of the client and all other implementations now read the clients version of the fields. In addition, internal support for multiple callbacks has been added to the client so the client tracking logic (done in lua.lsp) can be done more robustly instead of wrapping the user callbacks which may error. | ||
* | fix(lsp): re-add client.commands and mark private | Lewis Russell | 2024-02-12 |
| | |||
* | refactor(lsp): move more code to client.lua | Lewis Russell | 2024-02-11 |
| | | | | | | | | | | | | The dispatchers used by the RPC client should be defined in the client, so they have been moved there. Due to this, it also made sense to move all code related to client configuration and the creation of the RPC client there too. Now vim.lsp.start_client is significantly simplified and now mostly contains logic for tracking open clients. - Renamed client.new -> client.start | ||
* | refactor(lsp): add type annotations | Maria José Solano | 2024-02-10 |
| | |||
* | refactor(lsp): tidy up logging | Lewis Russell | 2024-02-08 |
| | |||
* | fix(lsp): set fallback client name properly | zeertzjq | 2024-02-08 |
| | |||
* | refactor(lsp): move client code to a regular Lua class | Lewis Russell | 2024-02-07 |
Problem: The LSP client code is implemented as a complicated closure-class (class defined in a single function). Solution: Move LSP client code to a more conventional Lua class and move to a separate file. |