LSP
LSP copied to clipboard
Client implementation of the Language Server Protocol for Sublime Text
Make use of auto-generated types from https://github.com/sublimelsp/lsp-python-types that utilize [`NotRequired`](https://peps.python.org/pep-0655/) for properties that might not be present. https://github.com/sublimelsp/lsp-python-types generates two separate files - `lsp_types.py` and `lsp_types_sublime_text_33.py`. Former uses new class...
I've noticed that this weird thing is happening with code lens annotations on moving the cursor: https://user-images.githubusercontent.com/153197/190275044-6db9ace3-c2c1-4097-a741-eefe14cb14ba.mov - there is no relevant communication with the server on moving the cursor...
In vi mode, if I press `x` here, the 7 will be removed, so now the cursor is on the 7, I guess it's inlay hints cause this  another...
**Describe the bug** The console shows exceptions when using LSP-jdtls related to code actions. ``` Error handling None Traceback (most recent call last): File "/home/lucas/.config/sublime-text/Packages/LSP/plugin/core/sessions.py", line 1977, in on_payload handler(result)...
**Describe the solution you'd like** I would like to be able to filter out by symbol type on the "Go To Symbol" command. **Additional context** I most likely do not...
It's annoying that the hints stay visible for a short while when a region is removed. Can anything be done about this? https://user-images.githubusercontent.com/2431823/122651017-681b7080-d136-11eb-8a95-e81e35ce209f.mov
**Describe the bug** When having `show_diagnostics_panel_on_save` enabled, the panel will open only if the current file has diagnostics (diagnostics in other files are not considered) but when it does open...
See: https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#completionList
**Current:** Currently when changing workspace "settings" key, the server is restarted. **Expected:** I expect the the server to not restart when chaining the "settings" key, but rather LSP to send...
I went ahead and created a draft what I would imagine as alternative to #2023. Probably needs some thorough testing, but seems to work pretty well so far. I like...